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

No annotations are provided, so the description carries the burden. It adds useful context like the cost (0.01 USDC) and the static HTML focus, but does not disclose behavior such as redirects, timeouts, or error handling, which are typical for a fetch tool.

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 two short sentences, front-loaded with the primary purpose and followed by a clear cost statement. Every word earns its place with no 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?

For a simple two-parameter tool, the description covers purpose and cost but omits the return format and failure behavior. Since there is no output schema and no annotations, a bit more detail about response type or limitations would make it complete.

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 50% (only 'url' has a description). The description does not elaborate on the 'method' parameter or add syntax details beyond the schema. It reinforces the URL purpose but does not compensate for the missing method semantics.

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 ('raw HTML content from any web page'). It also distinguishes itself from sibling tools like fetch_api and fetch_pdf by emphasizing 'raw HTML' and 'static HTML scraping'.

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?

Provides clear use context with 'Best for static HTML scraping', but does not explicitly state when to avoid this tool in favor of alternatives. The guidance is implied rather than exclusionary.

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