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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavioral context that annotations cannot convey: a hold-first billing model where you are charged only for what is returned and failures are free. It still omits latency, rate limits, and the fact that default gl/location silently target the UAE/Dubai.

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?

Purpose and scope are front-loaded, and the second sentence covers cost behavior efficiently with no filler. The first sentence is a long run-on list of somewhat jargon-heavy deliverables ('Vera contacts payload'), which costs some readability but every clause carries information.

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 deliverable enumeration usefully substitutes for describing return content. But for a 10-parameter, open-world tool with 10% schema coverage, the description leaves critical calling details (location/gl defaults, depth/fresh semantics, engine choice) undocumented, so an agent cannot call it optimally.

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 only 10% (just idempotency_key), and 10 parameters exist, yet the description names only 'query' and 'brand'. Non-obvious parameters such as gl ('ae'), location ('Dubai'), engine, depth, and fresh are left entirely unexplained in both schema and description, so the description fails to compensate for the coverage gap.

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 gives a specific verb ('Run ... for a topic query and brand') and enumerates concrete deliverables (citation probability score, Reddit/Quora threads, listicle PR targets, AEO gaps, markdown brief), which differentiates it from siblings like ai_answers or find_discussion_candidates. However, the opening clause largely restates the title, and no sibling is named explicitly, so the differentiation is inferred rather than stated.

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 stated inputs ('topic query and brand') imply when the tool applies, and the deliverable list implies a GEO/citation-analysis use case, but there is no explicit when-to-use versus google_serp, find_discussion_candidates, or ai_answers, and no exclusions or prerequisites.

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