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

No annotations exist, so the description carries full burden. It discloses captcha/bot-wall handling, which is a key behavioral trait. However, it omits important aspects such as whether the operation is read-only, if authentication is required, rate limits, or error responses for non-public URLs.

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, front-loaded sentence that immediately conveys the core action and a notable feature. It contains no unnecessary words or repetition, earning its place efficiently.

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?

With no output schema or annotations, the description must provide a complete picture for the agent. It fails to explain the return format (raw HTML string), the impact of 'max_chars', or potential pitfalls (e.g., large pages). This lack of detail could lead to incorrect invocation or unexpected truncation.

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 0%, so the description must compensate. 'Any public URL' adds context for the 'url' parameter (must be public), but 'max_chars' is not mentioned, leaving its purpose (truncation) and relationship to output unclear. Partial compensation reduces the score from the baseline of 4.

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 'Any public URL as raw HTML (captcha/bot-wall handled)' clearly states the tool fetches raw HTML from a URL and handles obstacles like captchas. It distinguishes from sibling tools like 'screenshot' (image output) and 'read' (likely text extraction), making its purpose specific and actionable.

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 offers no guidance on when to use this tool versus alternatives like 'read' or 'screenshot'. It does not mention exclusions (e.g., private URLs) or contexts where the tool is unsuitable, leaving the agent without comparative direction.

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