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

Annotations already indicate read-only, idempotent, and non-destructive behavior. The description adds meaningful behavioral context beyond annotations by stating the page reports 'whether this deployment can execute it', which is a useful runtime capability check.

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 dense sentence efficiently conveys the tool's purpose, resource path, and content scope. No redundant phrasing or filler; every clause contributes essential information.

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-parameter tool with no output schema, the description adequately covers the return content and the key deployment-execution flag. It could be more complete by explicitly naming alternatives for usage routing, but that falls under usage guidelines.

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% and the schema already describes the pattern parameter with examples. The description's mention of 'identifier or alias' closely mirrors the schema, adding little new semantic value beyond what the schema provides.

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 explicitly states the tool retrieves a single pattern page, identifies the resource format (/patterns/{pattern}.md), and lists the page's content (definition, aliases, fit hypotheses, failure modes, sources, deployability). This clearly distinguishes it from listing or searching tools.

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 it is for fetching a specific pattern by identifier or alias, but it does not explicitly contrast this with siblings like list_patterns or search. No when-not-to-use guidance or alternative suggestions are provided.

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