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

The annotations already disclose readOnlyHint=true, openWorldHint=true, and destructiveHint=false. The description adds useful context about what the breakdown contains (inbox providers like Gmail, Outlook, Yahoo) but does not discuss authentication, rate limits, pagination, or response shape.

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 tight sentence with no wasted words. The core resource and scope are front-loaded immediately.

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 single-parameter read tool with no output schema, the description adequately states the return concept. However, it leaves gaps around parameter semantics and usage alternatives that an agent may need when deciding whether to call this versus other campaign tools.

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 description coverage is 0%, and the single parameter campaign_uid is undocumented in the schema beyond its pattern and length constraints. The description mentions 'a campaign' but does not explain the parameter, its required status, or expected identifier format, so it does not compensate for the coverage gap.

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 return type: an inbox-provider breakdown of a campaign's delivery, with examples of providers. It distinguishes this from general campaign tools, though it does not explicitly name sibling alternatives such as mailblaze_get_campaign or mailblaze_get_campaign_summaries.

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 the tool is used to inspect delivery by inbox provider, but it gives no explicit when-to-use guidance, prerequisites, or comparison to alternative campaign reporting tools.

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