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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuine context beyond that: it discloses what is inspected (robots.txt per bot, llms.txt, 15 content checks, plain-text view), which tells the agent what work is performed and what data comes back. It does not mention that it fetches the live remote page or any latency/rate considerations.

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 main action and scope are front-loaded in the opening clause, and the parenthetical detail on the 15 checks is informative rather than filler. It is a single long sentence with heavy nesting, which costs some readability, but nothing is clearly redundant.

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, the description carries the burden of indicating what the tool returns, and it does sketch the return surface (per-bot robots results, llms.txt presence, citability signals, plain-text rendering). For a multi-check diagnostic tool this is close to complete, though it doesn't say how findings are grouped or whether scores are returned.

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?

There is one parameter with 100% schema description coverage, and the schema already explains the accepted format including bare domains, so the baseline is 3. The description adds nothing about the url parameter beyond what the schema provides.

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 names a specific verb and resource ('check whether AI crawlers may read a page') and enumerates the concrete sub-checks: per-bot robots.txt, llms.txt existence, 15 citability checks, and plain-text rendering. That composite scope implicitly separates it from narrow siblings like test_robots or validate_llms_txt, but no sibling is named, so the differentiation is left to inference.

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?

It gives a clear usage trigger with a real user question ('why does ChatGPT not mention my site'), which tells an agent when to reach for it. It stops short of exclusions or alternatives — it never says to use test_robots or ai_crawler_policy when only the crawler policy is in question, even though those siblings overlap.

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