List campaigns

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

Discloses read-only nature and 60-second caching, which are key behavioral traits. However, without annotations, it does not mention authentication requirements (though 'authenticated user' is stated) or pagination behavior beyond the schema.

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?

Two sentences efficiently cover purpose, usage, and caching. No extraneous text; front-loaded with the core action.

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 simple list tool with one optional parameter and no output schema, the description covers purpose, usage context, and caching. The missing documentation of the 'page' parameter is a minor gap given its simplicity.

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 description does not explain the 'page' parameter at all, despite 0% schema description coverage. The agent receives no guidance on how pagination works or how to use this optional 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 clearly states the tool discovers accessible Kanka campaigns and provides the campaign_id for subsequent operations, distinguishing it from siblings like kanka_get_campaign and kanka_list_entities.

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?

Explicitly advises calling this first to obtain campaign_id for entity-level operations and notes caching behavior (60 seconds) with a hint to recall if campaigns may have changed, providing clear when-to-use guidance.

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