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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states that JavaScript is not executed, redirects are followed, and SSRF, timeout, and response-size guards are applied. It does not mention the exact output format or error behaviors, but for a low-complexity fetch tool this is solid coverage beyond the obvious read-only nature.

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 exceptionally concise: two sentences. The first sentence lists the return content categories, and the second provides the alternative tool and salient behavioral guards. Every word adds value with no filler or redundancy.

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?

Given the low complexity (one required parameter, no output schema), the description fully covers the tool's purpose, output signals, alternative usage, and safety behaviors. It is complete enough for an agent to select and invoke the tool without missing critical information.

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 100%, so the baseline is 3. The parameter description adds meaningful usage guidance by reiterating when to use extract vs. read and noting no JavaScript rendering, which goes beyond a mere type/format definition. This adds practical semantics for selecting the right tool.

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 uses a specific verb ('Fetch') and clearly identifies the resource ('public HTTP(S) page') and the output (compact extraction signals: title, meta description, Open Graph/Twitter metadata, JSON-LD, headings, links, text excerpt, AI-readiness flags). It also distinguishes itself from the sibling tool 'read' by explicitly contrasting metadata/link inventory vs. full-body Markdown, which is strong sibling differentiation.

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 explicitly states when to use 'extract' (need metadata, JSON-LD, headings, links, text excerpt) and when to use 'read' instead (need the page body as LLM-ready Markdown). This directly addresses the main alternative among siblings and gives clear decision criteria.

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