@cg3/equip 0.2.12 → 0.2.13
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +12 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -141,6 +141,18 @@ const { detectPlatforms, installMcpJson, installRules, createManualPlatform, pla
|
|
|
141
141
|
- **Dry-run support** — Preview changes without writing files
|
|
142
142
|
- **CLI helpers** — Colored output, prompts, clipboard utilities included
|
|
143
143
|
|
|
144
|
+
## Limitations — Why Rules Matter (and Why They're Not Enough)
|
|
145
|
+
|
|
146
|
+
MCP tool descriptions alone don't reliably trigger agent behavior. [Research on 856 MCP tools](https://arxiv.org/abs/2602.14878) found that 97.1% of tool descriptions contain quality issues, and even fully optimized descriptions only improve task success by ~6 percentage points.
|
|
147
|
+
|
|
148
|
+
Behavioral rules (the `.md` files equip installs) are stronger — they live in the agent's system prompt or project context, closer to how agents make decisions. But they have limits too:
|
|
149
|
+
|
|
150
|
+
- **Context window compaction** can drop rules from the agent's working memory during long sessions
|
|
151
|
+
- **No platform hooks exist** to enforce tool calls — the agent always decides whether to act
|
|
152
|
+
- **No open standard** for server-initiated actions (MCP sampling exists in spec but isn't widely implemented)
|
|
153
|
+
|
|
154
|
+
Equip gives you the best available distribution: MCP config for tool availability + behavioral rules for usage guidance. For guaranteed tool invocation, platform-level middleware (IDE extensions, framework hooks) is required — but that doesn't exist as open infrastructure yet.
|
|
155
|
+
|
|
144
156
|
## License
|
|
145
157
|
|
|
146
158
|
MIT — CG3 LLC
|