diagnose_site

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

No annotations are provided, so the description carries the full burden. It only states purpose and usage time, but does not disclose whether diagnosis involves sending requests, potential side effects, or safety implications. 'Diagnose anti-crawling capabilities' implies probing but lacks explicit behavioral disclosure.

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 terse sentences, each serving a clear purpose: defining the tool's function and indicating when to use it. No redundant information.

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?

Given an output schema exists and there is only one parameter, the description provides the essential purpose and usage timing, but lacks details about the diagnostic process or prerequisites. It is minimally adequate but could be enriched with more context.

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 has a single 'url' parameter with 0% description coverage, and the tool description does not add any parameter-specific information. The agent gets no semantic guidance beyond the parameter name and type.

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 states a specific action ('diagnose') with a clear target ('website anti-crawling capabilities') and outcome ('recommend strategy'), distinguishing it from sibling tools like scrape_url and crawl_site.

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 explicitly says when to use it ('when first encountering a new site'), providing clear context. However, it does not mention alternatives or when not to use it, so it falls short of full explicit guidance.

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