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

Annotations indicate idempotentHint=true and destructiveHint=false. The description adds that the tool can write files (mode=write, reload), which is consistent with readOnlyHint=false. It does not mention side effects beyond file writing, but the modes provide behavioral context.

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?

Two sentences, no wasted words. First sentence states purpose, second explains modes. Every sentence adds value.

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?

No output schema, but the description explains the tool's operation and outcomes (recommendations, file generation) sufficiently. It doesn't detail return values, but for a file-writing tool, that is acceptable.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning by explaining the purpose of each mode in a sentence: 'Use mode=analyze to see recommendations, mode=write to generate CLAUDE.md, mode=reload to re-scan and update.' This goes beyond the enum labels and provides usage context.

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 the tool's purpose: analyzes project structure and generates a tailored CLAUDE.md. It uses specific verb-resource combinations and distinguishes modes (analyze, write, reload). It is distinct from sibling tools which focus on checks and audits.

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 explicitly explains when to use each mode ('Use mode=analyze to see recommendations, mode=write to generate CLAUDE.md, mode=reload to re-scan and update'). It provides clear context but does not mention exclusions or alternatives.

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