Compare against competitors

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

Annotations indicate readOnlyHint and openWorldHint; description adds critical behavioral details: each competitor costs an audit, quota management, ranking, skipped list, and over-quota error with reset time. No contradiction.

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?

Well-structured multi-sentence description that is compact yet informative. No wasted words; every sentence adds value.

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?

Given the complexity (quota, multiple competitors, error handling) and absence of output schema, the description explains return values (score, appearance, quota summary, skipped list) and edge cases well. Could specify exact output structure but sufficient.

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 baseline 3. Description mentions domain and competitors but adds no new meaning beyond the schema descriptions. The quota behavior relates to competitors but not parameter semantics directly.

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?

Description clearly states it compares AI visibility of a site against named competitors, using specific verbs and resource. It distinguishes from sibling tools like get_ai_visibility (single site) and get_benchmark (benchmarking).

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?

Explicitly states when to use: for head-to-head comparisons, like 'how do I stack up against X and Y.' It explains quota behavior and handling of insufficient quota but does not explicitly mention when not to use or alternatives beyond the context.

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