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

With no annotations, the description carries the full behavioral burden and delivers almost nothing: no indication of read-only nature, rate limits, pagination behavior (limit/offset), or how response_mode='compact' vs 'full' changes output. The only implicit signal is 'Compare', suggesting a read operation.

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?

One short, front-loaded sentence with no waste. However, brevity here is a symptom of under-specification rather than disciplined editing, so it does not reach 5.

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 deeply nested payload schema (4 operations, filters, ordering, pagination) and no annotations, the description is drastically incomplete. An agent cannot correctly invoke this tool from the description alone.

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% and the description compensates for none of it. Critical parameters -- payload.operation (the dispatcher), platform, location, language, filters, order_by, response_mode -- are never mentioned. The single sentence does not explain a single parameter.

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 the domain (app rankings, keywords, metrics, competitors) but reads as a list of possible features rather than a precise verb+resource. It fails to state that this is a single dispatcher tool with four operations, leaving the agent to infer that the 'operation' parameter selects the underlying behavior.

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 guidance on when to use this tool versus alternatives. The four operation values (bulk-metrics, keywords-for-app, app-competitors, app-intersection) in the schema are not mapped to the feature list in the description, so an agent has no signal about which operation corresponds to which capability.

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