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

Annotations already declare this as a safe, read-only, idempotent operation, and the description adds meaningful behavioral context: Cloudflare verification, exclusion of fake AI bots, and free vs PRO data limits. It does not cover auth requirements or rate limits, but the tier constraints are strong added value.

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 front-loaded with the core purpose and then adds the relevant operator, tier, period, and filtering details in compact form. Every sentence contributes useful information without unnecessary repetition.

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 provides enough return-shape context by listing operator names, per-bot counts, pages, formats, countries, and comparison data. It also explains free vs PRO behavior and the fake-bot exclusion, leaving no major gap for an agent to call it correctly.

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 description coverage is 100%, so both parameters are already documented in the schema. The description reinforces the days options and free-tier limitation, but adds little parameter semantics beyond what the schema already provides, which is the baseline for high-coverage schemas.

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 and resource: it shows which AI bots read one site, naming the operators, verification source, and comparison period. This clearly distinguishes it from generic sibling tools like get_site_stats by focusing on AI bot 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 description implies usage through the purpose and tier details, and explains that free accounts get 7 days while PRO supports 7, 30, or 90 days. However, it does not explicitly say when to use this tool instead of get_site_stats or other analytics siblings.

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