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

Annotations already declare readOnly, idempotent, and non-open-world behavior, so the safety profile is covered. The description adds useful context beyond that: the output is Markdown and the tool operates on exactly one page. It does not itself mention the truncation ceiling, though max_chars is documented in the schema.

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?

Three short sentences, front-loaded with the action and output format, then accepted inputs, then routing guidance. No filler; every sentence carries distinct 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 two-parameter read tool with full schema coverage, an output schema, and rich annotations, everything an agent needs is present: purpose, input forms, discovery alternatives, and return format. No significant gap remains.

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%, so the baseline is 3, but the description adds concrete accepted forms ('/pricing/', '/docs/getting-started/', absolute URL) that make the url parameter unambiguous beyond the schema's generic wording. The max_chars default/limit is left entirely to 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 verb and resource (fetch one page) plus the return format (Markdown) and the accepted input shape. It clearly differentiates from the sibling tools by positioning get_page as the reader and list_pages/search_site as discovery 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?

Explicitly routes the agent: 'Use list_pages or search_site to find URLs,' naming the alternatives and the condition that selects them. Combined with the accepted path/URL forms, an agent knows both when to call this tool and how to obtain its input.

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