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

With no annotations, the description carries the full burden. It usefully discloses that the operation is read-only and explains the reply classifications, but it does not mention pagination, permissions, or any limits on the result set.

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 tightly written sentence, front-loading the resource and including only classification clarifications that earn their 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?

It covers the core purpose, read-only nature, and classification semantics, which is adequate for a simple two-parameter list tool. It still omits pagination behavior, result limits, and explicit sibling routing, leaving some gaps for an agent to infer.

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 50%: the id parameter is described in the schema, while the type enum lacks a schema description. The description compensates by defining real, auto_reply, and bounce, which helps interpret the classification values, but it does not clarify whether type is used as a filter or how id relates to list_campaigns.

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 states a specific resource (email replies received by a campaign) and indicates the returned content (body and classification). It is clear what the tool lists, though it does not explicitly contrast with nearby siblings like list_campaign_emails or get_campaign_email.

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 purpose implies when to use it — inspecting replies received by a campaign — and 'Read-only' signals safe usage. However, there is no explicit guidance on when to choose this over alternatives such as list_campaign_emails or get_campaign_thread.

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