get_unsubscribe_report

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

No annotations are provided, so the description must convey behavioral traits. It mentions 'who unsubscribed and why' implying the data includes reason, but does not disclose pagination behavior (despite count/offset parameters) or that it is a read-only operation. Minimal additional context beyond the name.

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?

Single sentence, front-loaded with the key action and resource, no filler. Every word earns its place.

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 tool with an output schema, return values are not required. However, the description omits mention of pagination (count/offset) which is important for retrieving all unsubscribers. It is minimally adequate but would benefit from stating that it returns a paginated list of unsubscribers with reasons.

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 elaborate on any of the three parameters (campaign_id, count, offset). With 0% schema description coverage, the tool description should explain what count and offset control (e.g., pagination), but it fails to do so, leaving the agent to infer from defaults.

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 verb 'Get' and the resource 'unsubscribe details for a campaign', specifying what it returns (who unsubscribed and why). It distinguishes itself from sibling tools like get_campaign_report or get_open_report by focusing on unsubscribe data.

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?

No explicit guidance on when to use this tool versus alternatives like get_campaign_report or get_sent_to_report. The purpose is clear from the name and description, but there is no when-not-to-use or alternative suggestions.

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