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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds no behavioral context of its own — not what "top" means, not the ranking window, not whether omitting both product parameters returns a global list or an error.

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 phrase is front-loaded with zero filler, which is structurally sound. However it is under-specified rather than concise — one fragment carries the entire definitional burden for a two-parameter analytics tool.

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?

An output schema exists, so return values need not be described. But with 0% parameter documentation and no usage or ranking semantics, the description leaves the two ambiguous optional parameters and the scope of "top" completely unexplained for a tool that sits among dozens of similar analytics siblings.

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 says nothing about product_ref versus product_name, both of which are optional. It neither explains the difference between the two identifiers nor what happens when both or neither are provided, so the parameter ambiguity is left entirely unresolved.

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?

"Read top campaigns by spend" gives a verb (read) and a resource (campaigns) with a ranking metric, so the general intent is inferable. But "top" is undefined — no count, no time window, no ordering detail — and nothing distinguishes it from sibling insight/campaign tools such as insights_pull_product_breakdowns or campaigns_reconcile_campaign_plan.

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, no exclusions, and no named alternative among the many insights_* and campaigns_* siblings. The agent must guess whether this is a per-product reporting call or a general spend ranking.

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