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

Annotations already declare readOnlyHint/openWorldHint/destructiveHint, so the safety profile is covered. The description adds genuinely useful context beyond that: every reading carries its own sample count, and a change should be treated as indicative unless the sampling block licenses otherwise. That interpretive caveat is real behavioral guidance for reading the output, though pagination/limits are not discussed.

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 primary content is front-loaded in the first sentence, followed by the interpretation caveat and then the parameter tip. It is dense but each clause carries content; the only mild cost is the run-on enumeration in sentence one, which is long but not wasteful.

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 one optional parameter, no nested objects and no output schema, the description carries the burden of conveying what comes back, and it does so thoroughly, including the sampling caveat for interpreting changes. Nothing essential is missing for a read-only reporting tool.

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% and the lone parameter's schema description already spells out the drill-down behaviour ('Drill into one tracked question by its id (from the prompts list) for the engine answer text and citations'). The description's 'Pass prompt_id to drill into one question' largely restates that, adding no new meaning. Baseline 3 applies.

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 specific resource and enumerates its contents concretely: engine answers (ChatGPT, Gemini, Perplexity, Google AI Overviews), share of voice, cited sources, competitor-owned gaps, trend, crawlability and off-site reach. An agent knows exactly what data comes back. It does not, however, explicitly contrast itself with near-neighbours like get_scoreboard, get_seo or get_snapshot, so it stops short of a 5.

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 only operational instruction is 'Pass prompt_id to drill into one question', plus the meta note that it is read-only and free. There is no statement of when to reach for this tool versus the sibling reporting tools, and no exclusions or prerequisites. Usage is implied rather than stated.

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