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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so 'Does not change anything' is largely redundant repetition of structured data. The only added behavioral context is the 'once available' qualifier indicating answer-engine results may be absent initially, which is a small but genuine 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?

Two tight sentences, front-loaded with the primary purpose and followed by safety/routing info. No filler, though the 'Does not change anything' clause earns little since annotations already carry it.

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 an output schema present, return values need not be detailed and there are no parameters to document. The description covers scope and read-only nature adequately; naming concrete alternatives with conditions would have closed the remaining 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?

The tool takes zero parameters, so the schema baseline is 4. The description's enumeration of returned sections adds light value about scope but there are no parameters whose semantics need explaining.

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 read verb ('Shows') and enumerates the resource contents (buyer questions, AI search volume, referral traffic, readiness, answer-engine results), so an agent knows what comes back. It also names related tools, giving partial sibling differentiation, though the broad multi-section scope makes it harder to distinguish at a glance from check_ai_assistant_tracking or get_search_performance.

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 'Related:' list points at refresh_ai_volume, save_strategy_item and check_site_readiness, implying this is the read-side counterpart, but no explicit when-to-use vs when-not conditions are given. The relationship is left for the agent to infer.

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