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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description still adds real behavioral context by disclosing the shape of the payload — ready-to-save rule files in named formats, each rule citing its source incidents — which is more than the annotations provide. It omits whether this triggers analysis or reads cached results.

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?

A single front-loaded sentence with the default format stated first and the alternatives parenthesized; no filler, and the novel detail (incident citations) lands at the end where it is easiest to skim.

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?

With no output schema and no annotation coverage of return values, the description does explain what comes back (rule files plus supporting incident citations), which is enough for a simple read-only tool. It is thin only on the effect of 'mode' and on what the agent should pass as 'proposal'.

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 description coverage is 0%, so the description must carry parameter meaning, and it only partially does. It clarifies the 'format' enum by naming the concrete outputs (AGENTS.md default, CLAUDE.md, Cursor rule, Copilot instructions), but says nothing about the 'mode' enum (design vs existing_app) or what 'proposal' should contain.

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?

States a specific verb and resource ('Return ready-to-save rules') and names the concrete artifacts (AGENTS.md, CLAUDE.md, Cursor rule, Copilot instructions), so an agent knows exactly what it gets back. It does not, however, distinguish itself from siblings like analyze_design or analyze_existing_app, which appear to operate on the same inputs.

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?

'for a proposed design' implies the context of use, but there is no explicit statement of when to call this versus analyze_design/analyze_existing_app, nor any note that the 'mode' parameter switches between design and existing_app scenarios. Usage is inferable rather than stated.

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