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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds nothing behavioral beyond that—no default time window when from/to are omitted, no note on how 'engine' versus 'engines' interacts, and no hint about result size or limits for a 9-parameter read.

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?

A single front-loaded sentence with no filler and the data returned named immediately. It is efficient, though its brevity is partly the source of the coverage gaps rather than a deliberate trade-off.

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 9 parameters, 0% schema description coverage, no output schema, and a confusingly similar sibling, the description does far too little to let an agent invoke this correctly. Key decisions—single vs multiple engines, date defaults, comparison targets—are left entirely unspecified.

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 0% across 9 parameters, and the enums (engine/engines, category, sovScope) carry no explanation anywhere. The description loosely gestures at 'ranking of brands' (compare), 'share of voice' (sovScope), and 'head-to-head prompts', but leaves the critical engine vs engines distinction, date range semantics, and category meanings entirely undocumented.

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?

States a specific verb and resource ('Read the ranking of brands in AI answers, share of voice, and head-to-head prompts'), which tells an agent the payload shape. It does not, however, distinguish itself from the near-identically named sibling get_ai_visibility_competitor (singular), leaving an ambiguity the agent must resolve elsewhere.

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 which sibling to prefer for a related query. The 'compare'/'head-to-head' phrasing implies a comparison use case but never gates it against get_ai_visibility_competitor, get_ai_visibility_overview, or get_ai_sentiment_benchmark.

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