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

Adds behavioral details beyond annotations: states return format (Markdown) and inclusion of canonical URL. Annotations already declare readOnlyHint and idempotentHint, so safety is clear. The description adds value by specifying output structure and source of id, though it doesn't cover error handling or pagination.

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 concise sentences, with the main purpose front-loaded. No filler or redundant information. Every sentence earns its place.

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 simple one-parameter fetch tool with an output schema and read-only annotations, the description provides sufficient context: what it returns (Markdown + URL) and where the id comes from. Nothing critical is missing for correct invocation.

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 already covers the id parameter ('A page id returned by search'), and the description repeats this essentially verbatim. With 100% schema description coverage, the baseline is 3; the description adds no extra semantic meaning beyond the schema.

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 action (read page) and resource (905 Trades website page), and specifies output format (Markdown with canonical URL). It does not explicitly distinguish from siblings like get_business_facts or request_quote, but the 'full text of one page' is clear enough for most agents.

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?

Implies usage by stating 'The id comes from search,' which signals a dependency on a prior search call. However, there is no explicit guidance on when to prefer this tool over siblings, nor any when-not-to-use conditions. The usage context is present but not fully elaborated.

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