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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is fully covered. The description adds that each entry carries purpose and progress, which is genuine return-content context, but says nothing about ordering, pagination, or empty-project behavior.

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?

A single short sentence covering scope and payload with no filler. It could be slightly more front-loaded by leading with the verb ('Lists...'), but nothing in it is wasted.

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 parameterless list tool with no output schema, an agent still lacks basics like ordering, whether results are paginated, and how an empty project is represented. The description is adequate but leaves those gaps unaddressed.

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?

With zero parameters, there is nothing to document and 100% schema coverage is by definition. The description correctly implies a no-filter full listing, so it neither misleads nor omits anything actionable.

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 resource (campaigns), the scope (in this project), and the payload (what each is for, how far through it is), so an agent can infer it returns all campaigns with purpose and progress. However, it's a noun phrase with no explicit verb such as 'list' or 'returns', leaving the operation type implicit rather than stated.

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 guidance on when to use this versus get_campaign, edit_campaign_plan, or pause_campaign, all of which appear in the sibling list. The word 'campaigns' plural hints at listing everything, but no exclusions or alternatives are given.

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