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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds specific behavioral details: output format (Markdown or stripped text), a character limit (40,000), and domain restriction (michaelbarber.tech). This enriches the behavioral context beyond what annotations provide, though it does not mention error handling or truncation behavior.

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?

The description is a single, front-loaded sentence with no redundant words. It states the core action first, then adds format and limit details. There is no filler or unnecessary 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 simple read tool with one parameter and safety annotations, the description is largely sufficient. It specifies the target domain, output format, and size limit. Missing details like behavior on inaccessible pages or exact meaning of 'stripped text' are minor given the tool's simplicity and the annotations covering read-only and idempotent behavior.

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 0%, so the description must compensate. It adds the domain restriction (https://michaelbarber.tech) and clarifies the URL is a page from that site. However, it does not elaborate on the parameter's format beyond the schema's URI type, leaving some ambiguity about required URL structure (e.g., trailing slashes, query strings).

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 clearly states the tool reads a single page from a specific domain (michaelbarber.tech) and outputs Markdown or stripped text. It distinguishes itself from siblings (search_pages, site_info) by explicitly focusing on content retrieval rather than searching or site-level metadata.

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 provides no guidance on when to use this tool versus its siblings. It does not mention search_pages or site_info as alternatives, nor does it give any conditions for selection. The only implied context is that it is for reading page content, which is insufficient without explicit routing.

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