List campaigns

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds genuinely non-obvious behavior: archived campaigns are hidden by default and search/sort/archived filter require Plunk v0.15+. It also sketches the return payload, though pagination semantics aren't described.

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?

Bold-labeled sections make it scannable and front-loaded with purpose before caveats. Slightly label-heavy for its length, but every sentence carries distinct information (exclusion, return shape, trigger, version caveat).

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?

Covers purpose, alternative, trigger, return shape and a version/default-filter caveat for a 7-param list tool with no output schema. Remaining gap is pagination behavior (pageSize/dir), which the description never addresses.

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 coverage is only 29% (7 params), so the description must compensate and it only partially does: it explains the archived flag and mentions search, sort and the status filter. dir, page and pageSize are left entirely to uninformative schema entries, though they are conventional pagination params.

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?

States a specific verb and resource (list campaigns) plus scope (status states draft/scheduled/sending/sent) and explicitly distinguishes itself from plunk_get_campaign_stats. An agent can tell it apart from the other campaign siblings without opening any 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?

Has an explicit 'Not for' exclusion naming the alternative tool, and a 'Use when' clause giving the triggering conditions (need a campaign id, user asks what campaigns exist or is scheduled). This is the when/when-not/alternative pattern done fully.

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