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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds no behavioral context of its own: no indication of live querying versus cached results, credential or API-key needs, run cost/duration, or how scores are computed. It also repeats itself verbatim (truncated blurb followed by the same blurb extended), which reads as marketing copy rather than operational disclosure.

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 literally the same sentence twice — a truncated version followed by an expanded version — with the lead-in buried in an ellipsis. No part of it is front-loaded around the actual task; the duplication is pure waste.

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 tool with a nested input object, no output schema, and no annotation detail beyond read-only/open-world, the description leaves too much unspecified: what inputs it accepts, what the report contains beyond four metric names, and how long a run takes. The metric list is the only substantive content and it is not enough for confident invocation.

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?

There is a single nested `input` object with 100% schema description coverage, so the schema technically carries the burden — but that coverage is only a URL pointer to the Apify listing, adding no real meaning. The description supplies zero guidance on what to configure (brand, competitors, prompts, models), so an agent must leave the input empty and cannot tailor the run.

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 names a clear subject — whether ChatGPT, Perplexity, Gemini and Google AI Overviews recommend your brand versus competitors — and enumerates the metric families (visibility, share of voice, citations, fact accuracy). It does not, however, differentiate itself from close siblings such as ai_brand_visibility, ai_share_of_voice, ai_brand_accuracy and ai_citation_miner, each of which appears to cover one of the listed metrics.

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?

There is no statement of when to use this tool, when not to, or what to pick instead. Given that four sibling tools name nearly identical concepts (ai_brand_visibility, ai_share_of_voice, ai_brand_accuracy, ai_citation_miner), the absence of routing guidance is a real cost — an agent cannot tell which of these to call.

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