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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It covers JavaScript non-execution, shell-page detection via character count, honest blocking reporting, output cap behavior, and pricing/cost details. This is far more transparent than the typical tool description.

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 dense but efficiently structured: core behavior first, usage guidance second, behavioral caveats next, and cost last. No sentence is filler; each adds distinct operational information an agent needs.

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?

There is no output schema and no annotations, yet the description tells the agent what will be returned, how to adjust limits, what the failure modes are, and even the cost implications. For a read-only page-fetching tool, this is complete enough for correct invocation and expectation-setting.

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 real value beyond the schema: it explains the output cap semantics, how maxChars relates to prompt-fit, and how the character count can indicate client-side rendering. This contextualizes parameters rather than merely restating their schema types.

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 opens with a specific action and resource: 'Fetch a URL and return its readable text,' and enumerates the exact outputs (title, description, site name, publication date, stripped content). This is unambiguous and clearly distinguishes the tool from a search or link-extraction utility.

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 explicitly says 'Use whenever you need the contents of a page rather than a search result about it,' giving a clear invocation context. It does not explicitly name sibling tools or when NOT to use it, but the usage rule is actionable and sufficiently scoped.

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