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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context: it removes clutter (navigation, scripts, cookie UI) and discloses a cost of $0.01 per page, which is important for agent decision-making. No contradiction with annotations. It could mention error handling or rate limits, but given the annotation coverage, a 4 is appropriate.

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 three sentences, each earning its place: the first states the core action and output, the second gives the usage condition, and the third discloses cost. Information is front-loaded and there is zero fluff. It is appropriately sized for the tool's simplicity.

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?

The tool has an output schema (not shown but indicated), so return values need no explanation. The description covers purpose, usage, behavior (cleaning), and cost. It does not mention authentication or rate limits, but for a public-page fetch with read-only semantics and a single parameter, these are minor gaps. Overall, an agent can correctly decide to call this tool without needing additional details.

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 0% (no description for the 'url' parameter), but there is only one parameter with format 'uri' which is self-explanatory. The description implies that the URL must be public and is the target of fetching. It adds the context that the page must be publicly accessible, which goes beyond the schema. For a single trivial parameter, the description sufficiently compensates for the lack of schema-level documentation.

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 explicitly states the action (fetch a public webpage) and the output (compact agent-ready Markdown, canonical metadata, tables, important links) while also listing what it removes (navigation, scripts, cookie UI, layout clutter). This distinguishes it clearly from sibling tools like website_accessibility_auditor or website_change_monitor, which have different purposes. The verb+resource is specific and unambiguous.

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 gives a clear usage condition: 'Use when you need readable content from a public webpage without navigation or page clutter.' This tells the agent when to invoke the tool. However, it does not explicitly mention alternatives or when not to use it, though the sibling list implies different tools for other tasks. Since it provides a clear trigger without exclusions, it earns a 4.

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