list_campaigns

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

No annotations are provided, so the description carries the full burden. It only says 'List' and includes the GET endpoint, which implies read-only behavior, but it does not mention pagination, ordering, authentication, rate limits, or whether the results are complete. The pagination-relevant parameters (after, before, limit) are not explained.

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 compact sentence with no filler, and including the endpoint is useful. It is front-loaded and easy to parse, though it is minimal to the point of under-specification.

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 no annotations, no output schema, and opaque pagination parameters, the description is not complete. It leaves unanswered when to use this tool, how pagination works, and what the response contains. The low parameter coverage makes it insufficient for correct invocation in non-default cases.

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 does not explain any of the three optional parameters: after, limit, before. An agent cannot determine cursor semantics, value formats, or how parameters interact. The description adds no meaning beyond the raw parameter names in the schema.

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 states a specific verb ('List') and resource ('campaigns'), and also includes the HTTP endpoint 'GET /campaigns' to remove any ambiguity. It is clearly distinct from related sibling tools such as get_campaign or list_templates.

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 like get_campaign, get_campaign_stats, or list_polls. There is no mention of intended use cases, exclusions, or selection criteria relative to sibling tools.

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