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

Annotations already declare readOnlyHint and openWorldHint, and the description adds genuinely new behavioral context: the check is limited to robots.txt and a firewall may still block a bot despite a permissive result. That scope limitation is the kind of caveat an agent could otherwise misreport. It stops short of describing the shape of the result (e.g., per-bot verdicts or matched directives).

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?

Two tight sentences: the core behavior and covered bots come first, the optional narrowing second, and the scope caveat last. Nothing is repeated and no sentence is 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?

For a two-parameter read-only check with full schema coverage and no output schema, the description covers purpose, scope, and the main limitation that could cause a wrong conclusion. Only the form of the returned verdict is left unstated, which is a minor gap given the simple answer the tool produces.

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 100%, with the bot enum fully documented inline and the url example given in the schema. The description's 'optionally limit the answer to one bot' merely restates the bot parameter, adding no syntax or edge-case detail beyond the schema. Baseline 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?

States a specific verb and resource ('check whether a site's robots.txt allows or blocks AI crawlers') and even enumerates the crawler families covered, so the agent knows exactly what is being tested. It does not explicitly contrast itself with the sibling check_ai_readiness, so the distinction must be inferred from the robots.txt framing.

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 'Optionally limit the answer to one bot' sentence gives a light usage cue, and the firewall note sets expectations about the answer. There is no explicit when-to-use / when-not guidance and no pointer to check_ai_readiness for broader readiness questions, so routing is only implied.

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