stealth_dom

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 only mentions 'bypassing simple IP blocks' but does not explain what this bypass entails, potential failures, request modifications, or what the response contains (e.g., raw HTML). This is a significant gap for a specialized 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 a single sentence, front-loaded with the action and key differentiator. Every word earns its place with no redundancy or filler.

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 a specialized behavior (bypassing IP blocks) but no output schema or annotations. The description does not explain the return format, limitations, or edge cases, leaving the agent without enough information to fully trust the tool's invocation.

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 input schema covers 100% of parameters, with 'url' described as 'Target URL to fetch'. The description does not add any parameter semantics beyond the schema, so the baseline score of 3 applies.

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 clearly states a specific action ('Fetch web pages') with a distinct qualifier ('from Cloudflare edge bypassing simple IP blocks'). This distinguishes it from all sibling tools, which focus on scrubbing, denoising, sentiment, or embedding.

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 context for when to use the tool: when fetching pages protected by Cloudflare with simple IP blocks. However, it does not explicitly mention alternatives or when not to use it, though no sibling tool performs a similar fetch function.

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