get_campaign_report

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

With no annotations, the description carries the full burden. It discloses that the tool returns metrics (opens, clicks, bounces, unsubscribes) and implies read-only behavior via 'Get', but it does not explicitly confirm side-effect-free operation, authentication requirements, or error handling for unsent campaigns.

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 concise sentence, front-loaded with the core action and resource, followed by a list of report contents. No wasted words or redundant information.

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 one-parameter tool with no output schema, the description adequately explains the purpose and gives a glimpse of return data. It lacks details on output structure and possible error states, but these are less critical given the tool's simplicity and the clarity of 'performance report'.

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 100% for campaign_id, but the description adds meaningful constraint: the campaign must be 'sent'. This clarifies that only sent campaigns are valid inputs, which is not present in the schema description.

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 uses a specific verb ('Get') and resource ('performance report for a sent campaign') and enumerates the report contents (opens, clicks, bounces, unsubscribes). It clearly distinguishes this reporting tool from sibling tools like list_campaigns or send_campaign.

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 implies when to use the tool (for performance reports on a sent campaign) but does not explicitly state alternatives, exclusions, or when not to use it. No comparison to sibling tools or prerequisite conditions beyond 'sent campaign' is provided.

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