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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds value beyond them by disclosing the return format (Markdown) and the scoping constraint (canonical public pages only), which is not in any structured field; error behavior for invalid paths is still unstated.

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 short sentences, purpose first, input sourcing second, with zero filler and a concrete example inline.

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 read tool with full annotations, the definition covers purpose, input source and output format despite there being no output schema. It omits what happens on an invalid or non-canonical path and whether long pages are truncated, which are minor for this tool.

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?

The schema has 0% description coverage for the single 'path' parameter, so the description must compensate, and it does: it states the expected format with a concrete example ('/pricing') and its provenance. It could have noted the 200-character limit or casing rules, keeping it from a 5.

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?

Specific verb+resource: reads a canonical public page and states the output format (Markdown). It explicitly ties itself to the sibling fabricate_search_pages as the source of valid paths, so an agent can route between the two without opening either schema.

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?

Gives clear usage context: the path must come from fabricate_search_pages, which effectively tells the agent to search before reading. No explicit when-not-to-use or failure conditions are given, so it stops short of a 5.

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