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

Annotations already declare readOnly, openWorld, and idempotent hints, but the description adds substantial behavioral context: unknown URLs cost nothing and schedule themselves, known URLs are metered, results are observational from a datacenter vantage, and a user-agent is a claim, not a credential. This goes well beyond the annotations.

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 compact yet information-dense, front-loading the primary purpose before adding cost, scheduling, and reliability caveats. Every sentence earns its place without unnecessary 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 batch triage tool with rich annotations and a simple one-parameter schema, the description covers purpose, result categories, cost behavior, scheduling, and reliability limitations. The lack of an output schema is mitigated by the description clearly indicating a summary to branch on before spending a fetch.

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% (the 'urls' parameter is described as up to 200 URLs, http or https), so the schema carries the parameter documentation burden. The description adds behavioral context about unknown versus known URLs but no additional parameter-level meaning, matching the baseline of 3.

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, batch-oriented verb and resource: 'Check up to 200 URLs in one call for AI-crawler access.' It also names the distinct output categories (readable, refused, tollgated), which clearly distinguishes this triage tool from single-URL or monitoring siblings like verify_ai_crawler or watch_ai_crawler_access.

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 gives clear usage context: use this before spending a fetch, with unknown URLs scheduling for free and known URLs metered. It does not explicitly name sibling alternatives or state when not to use the tool, so it falls just short of a 5.

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