list_campaigns

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

There are no annotations, and the description only states it lists sent campaigns—a read operation—without providing any behavioral details such as pagination, rate limits, or what happens if no campaigns exist.

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 description is a single, front-loaded sentence with no extraneous words, efficiently conveying the core purpose.

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?

Given the tool's simplicity and lack of output schema, the description adequately covers the basic purpose but omits what the returned data looks like (e.g., list of campaign objects or IDs), leaving some ambiguity.

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 100% schema description coverage, baseline is 3. The description adds no additional meaning beyond the schema, merely referencing the client without elaborating on the 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 'List all sent campaigns' uses a specific verb ('List') and resource ('sent campaigns'), clearly distinguishing it from sibling tools like 'list_draft_campaigns' and 'list_scheduled_campaigns'.

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 description provides no guidance on when to use this tool versus alternatives (e.g., list_draft_campaigns, list_scheduled_campaigns) or any prerequisites beyond the implicit client_id context.

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