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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered upstream. The description adds the dual list/read behavior, which is genuinely beyond the annotations, but says nothing about size of results, truncation, or whether missing paths error or return empty. With annotations carrying most of the burden, this is adequate rather than rich.

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, zero padding, and the primary read behavior is front-loaded ahead of the no-path fallback. Every clause conveys information an agent needs.

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?

For a single optional-parameter read tool with full annotation coverage and no output schema, the definition covers what is fetched, the path format, and the no-argument fallback. The only gap is what a successful read returns (full article body versus metadata), which the phrase 'reference articles' only loosely implies.

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 100% and there is only one optional parameter, so the baseline would be 3-4. The description goes beyond the schema's terse 'The guide's path.' by supplying a concrete format example (seo/audit.md) and, importantly, the semantics of omitting the parameter entirely, which the schema never states.

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 gives a specific verb (read) and resource (Fudge's reference articles) and explicitly covers the two modes: fetch by path or list all when the path is omitted. It does not, however, distinguish itself from the sibling get_design_guide, so an agent still has to infer which guide-ish tool applies to a given request.

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?

'Without a path, lists them all' clearly tells the agent how to get the catalog versus fetch a single article, which is real usage guidance for this tool's two modes. There is no statement of when to prefer this over get_design_guide or read_work, and no exclusions, so guidance stops short of full routing.

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