List campaigns

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful behavioral context beyond annotations: results are ordered newest first, status/audience size are exposed, content lives in the dashboard, and drafts are runnable via sendkuy_start_campaign.

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 two efficient sentences with no filler, and the core behavior is front-loaded. Every sentence earns its place by adding ordering/returned-field context or operational workflow context.

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 paginated list tool with a complete input schema, an output schema, and rich annotations, the description is complete enough. It adds the key non-schema context an agent needs: ordering, returned fields, where campaign content is authored, and the start-campaign workflow.

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 100%, so limit and cursor are fully documented in the input schema. The description does not add parameter-specific meaning beyond that baseline, which is acceptable given the schema already handles it.

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 and resource ('List campaigns') and adds ordering and key returned fields ('newest first, with their status and audience size'). It is clearly distinguishable from get_campaign and start_campaign, and an agent can tell what this tool provides without opening the schema.

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 gives clear workflow context: campaign content is authored in the SendKuy dashboard, and a draft found via this list is ready to run with sendkuy_start_campaign. It does not explicitly state when to prefer get_campaign or other sibling list tools, so it stops short of full alternative guidance.

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