am_i_cited

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

No annotations provided, so the description carries full burden. It mentions cost implications and auto behavior, but lacks disclosure on rate limits, quotas, or idempotency. A moderate score as it adds some behavioral context.

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 succinct sentences with clear front-loading of purpose. Every sentence adds value, and no wasted words.

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 (3 params, no output schema), the description covers purpose, usage, and parameter nuances adequately. It mentions output structure (per-query presence, rank, summary) but could elaborate on response format. Minor gap.

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%, but the description adds value by explaining the 'auto' engine behavior and clarifying that 'bing_serp'/'brave_serp' measure web rank, not LLM citations. This goes beyond schema.

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 clearly states the tool checks if a domain is cited by AI engines across queries, returning per-query presence, rank, and citation-rate summary. It distinguishes from sibling 'check_citations' by referencing it in the engine parameter.

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 provides explicit usage: 'Use to measure visibility for a brand, product, or content site in AI search.' It also advises pinning to a specific engine to reduce cost and directs web rank queries to 'check_citations'.

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