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

Annotations already mark it read-only, idempotent, and non-destructive; the description adds a 40,000-character cap and the two return representations. This gives useful expectations about output length and format, though it doesn't cover error behavior or redirects.

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 sentence conveys target, scope, output format, and length limit with no filler. All details are compressed and front-loaded around the verb 'Read.'

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 one-parameter, read-only fetch tool with no output schema, the description gives enough to invoke it: the URL shape, return format, and size cap. It doesn't mention error behavior, but annotations and the small surface area make that a minor gap.

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 only says 'url' is a URI, so the description's 'one https://asgolfclothing.com page' supplies the key constraint that the URL must point to a page on that domain. It doesn't explain the meaning of 'stripped text' or any URL formatting requirements, leaving some semantics implicit.

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 names a precise operation ('Read one page'), the exact target domain, and the output forms (Markdown or stripped text). Saying 'one page' distinguishes it from sibling tools that search pages or provide site info, so an agent can select it without opening the 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?

It clearly implies the tool is for fetching a single page from asgolfclothing.com, which complements search_pages (finding pages) and site_info (site-level info). It doesn't explicitly state when to prefer an alternative or list exclusions, so it stops short of full routing guidance.

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