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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds only that the tool explains robots.txt blocking consequences and that omitting the name enumerates tracked crawlers — useful but modest, and the enumeration behavior is already stated in the schema.

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 sentences, no filler. The core purpose and its subfields come first, and the calling instruction follows — well front-loaded and tightly sized for a one-parameter lookup tool.

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 a rich annotation set, an output schema, and one optional parameter, the description covers what the tool explains and how to call it. The only gap is guidance on choosing this tool over its siblings, which is minor for a simple explanatory lookup.

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 a single optional parameter with 100% schema description coverage, so the baseline is 3. The description supplies concrete examples (GPTBot, OAI-SearchBot) and the omit-to-list-all semantics, but the schema already documents both.

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 verb ('Explains') and resource ('AI crawler user agent') and enumerates the payload: operator, purpose, and the effect of robots.txt blocking. That content profile clearly separates it from check_ai_crawlers, get_ai_visibility_report, and view_page_as_ai_crawler, though no sibling is named explicitly.

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?

'Pass a name such as GPTBot or OAI-SearchBot, or omit it to list all crawlers Siteiz tracks' gives invocation guidance for the parameter, but says nothing about when to reach for this tool over check_ai_crawlers or the visibility report. Usage is implied rather than framed against alternatives.

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