get_campaign_recipients

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

With no annotations provided, the description must fully disclose behavioral traits. 'Get' implies a read-only operation, which is correct, but there is no mention of error handling (e.g., invalid campaign ID), rate limits, or any side effects. The behavior is basic and transparent enough for a simple query, but lacks depth.

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 sentence of 6 words, conveying the essential purpose without any filler. Every word earns its place, achieving maximum conciseness.

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?

Despite having 4 parameters including pagination (limit, offset), the description does not explain that the results are paginated, what the output format looks like, or that status filtering is available. The tool has moderate complexity and no output schema, so the description should provide more context about the return structure and usage patterns.

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 covers 100% of parameters with descriptions. The description adds no new meaning beyond 'for a specific campaign', which reinforces the required campaignId but is already implicit in the schema. Baseline is 3 due to high schema coverage.

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 action ('Get') and the resource ('recipient list for a specific campaign'). It distinguishes itself from sibling tools like 'get_email_campaigns' (which retrieves campaign metadata) and 'get_campaign_analytics' (which returns statistics).

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 no guidance on when to use this tool versus alternatives (e.g., when to use this over 'get_contacts' or 'get_email_campaigns'). There is no mention of prerequisites, such as requiring a valid campaign ID, or exclusions.

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