get_campaign_unsubscribes

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

With no annotations, the description fully discloses behavior: authentication method, concurrency limit (max 10), read-only safety, error handling (404), and empty results for unsent campaigns. This is comprehensive beyond what the schema provides.

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 well-organized into sections (purpose, usage, args, returns) but slightly verbose. Each sentence earns its place, though minor trimming could improve 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?

Given the presence of an output schema, the description still adds value by detailing the return format (JSON with total_items and unsubscribes array) and individual fields. Combined with behavioral details, it provides complete context for usage.

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?

Despite 0% schema description coverage, the description thoroughly explains each parameter: campaign_id with example and condition, count with range and default, offset for pagination. This adds significant meaning beyond the bare 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 begins with a clear verb and resource: 'Retrieve members who unsubscribed from a specific sent campaign.' It distinguishes from siblings like get_campaign_report for aggregate counts and get_campaign_recipients, making the purpose distinct.

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 mentions when to use an alternative tool: 'Use get_campaign_report for aggregate unsubscribe count instead.' Also specifies prerequisites (must be a sent campaign) and error conditions (404 for invalid campaign_id), providing clear usage context.

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