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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add context. It does so by stating the taxonomy of purposes and that robots.txt compliance and verification guidance are included per entry, which tells the agent what insight the response carries rather than just its shape.

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?

Front-loaded with the core action and resource, followed by a payload sentence and a usage sentence. The opening sentence is dense but every clause names a distinct returned field; no filler or restatement of the title.

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 an output schema present and annotations covering behavior, the description needs only to explain intent and payload concept, which it does. It omits the obvious default (no filters returns the full catalog), a minor gap for a zero-required-parameter list tool.

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%, so the baseline is 3; the description earns extra by glossing the purpose enum values in plain language ("builds a search index, fetches a page when a user asks, or collects training data"), which is semantically richer than the raw enum tokens search/user-triggered/training.

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?

Uses a specific verb (List) with a specific resource (AI crawlers) and enumerates exactly what each entry carries: operator, purpose, robots.txt behavior, docs, verification. This clearly separates it from siblings like check_ai_crawlers (one bot check) and get_crawler_activity (observed traffic).

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 three example questions give concrete entry points ("what is OAI-SearchBot?", "which bots does ChatGPT use?") that map naturally to the company and purpose filters. It doesn't explicitly exclude adjacent siblings like generate_ai_robots_rules, which also touches the 'which bots should I allow' question, so an agent must infer the boundary.

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