list_campaigns

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

The description discloses read-only behavior, which is a key trait since no annotations are provided. However, it does not mention pagination, rate limits, or other behavioral aspects beyond the simple read nature.

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 concise sentence. The parenthetical adds useful context but slightly clutters the main purpose. It is front-loaded efficiently.

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 presence of an output schema (not shown), the description is minimally complete for a simple listing tool. However, it lacks details on pagination, ordering, or error handling, which could be important for agent decision-making.

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?

The schema has 2 parameters (limit, offset) with defaults but no descriptions. The description does not explain their meaning or usage, leaving the agent to infer common pagination behavior. With 0% schema description coverage, this is a significant gap.

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 clearly states the tool lists email campaigns and notes it's read-only, which distinguishes it from creation tools. However, the phrase 'limited create support' is vague and not directly relevant to the listing purpose.

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 implies usage for listing campaigns but does not provide explicit guidance on when to use this vs. get_campaign, create_campaign, or other listing tools. No exclusions or alternatives are mentioned.

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