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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds only the ranking metric 'by spend'; it does not clarify what 'top' means, limits, pagination, or any auth context beyond the annotation baseline.

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 single front-loaded sentence uses no filler and is appropriately brief for a simple read operation. It is structured as a fragment, however, and leaves no room for the scoping or parameter details an agent would need.

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 explained, and annotations cover safety. But with three undocumented parameters, no usage guidance, and no product scoping, the description is too thin for an agent to invoke the tool correctly.

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?

All three parameters (product_ref, product_name, connection_context) have 0% schema description coverage, and the description mentions none of them. The agent has no explanation of what product_ref/product_name accept or what connection_context is, so parameter meaning is absent.

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 clear verb (Read) and resource (top campaigns) with a ranking metric (by spend), so the basic action is legible. However, it does not mention product scoping despite the tool name, nor differentiate this from sibling campaign/product retrieval tools.

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?

No when-to-use guidance, no alternatives named, and no prerequisites are given. An agent cannot tell from the description whether to use this versus campaigns_quick_create or products_get_health.

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