install-claude-md

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that the tool uses smart-merge by default (preserving customizations) and mentions replace and dryRun options. However, it does not cover all edge cases like error handling or directory creation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, under 200 characters, and front-loaded with the purpose. Every part is necessary and clearly written.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema and simple parameters, the description covers the core functionality well. It explains the merge behavior, but lacks detail on error conditions or prerequisites (e.g., plugin must exist). Still, it is largely sufficient for a straightforward tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema coverage is 100%, so baseline is 3. The description adds value by explaining the behavior of the 'replace' parameter (smart merge vs. full replace) and 'dryRun' as preview mode. This goes beyond the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it installs a CLAUDE.md in an existing Metalsmith plugin with smart-merging to preserve user customizations. This distinguishes it from sibling tools like 'audit-plugin' or 'configs' which have different purposes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use the tool (install CLAUDE.md), but does not explicitly state when to use alternatives or provide exclusionary guidance. Usage is implied by the purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.