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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered by structured data. The description's contribution is disclosing the return payload composition (bodies, schedule, cached sent/open/click counts), which is genuinely useful. It adds nothing about error behavior for an unknown id or the fact that counts are cached and possibly stale, so it does not exceed a moderate score.

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?

A single dense sentence front-loads the return contents, followed by a short endpoint reference. Efficient with no filler, though the endpoint notation is partially redundant with the tool name.

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?

With no output schema, the description carries the burden of describing the return shape and does so thoroughly for a one-parameter read tool. Missing only ancillary details such as behavior on a nonexistent or archived campaign id.

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% and the single parameter is fully documented with accepted string/integer forms and the note that it comes from the list tools. The description only echoes the parameter as a path segment ({id}), adding no syntax or edge-case detail beyond the schema, so the baseline 3 applies.

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 enumerates the exact fields returned from a single campaign (name, subject, bodies, sender, state, schedule, lists/segments, cached counts) and names the endpoint GET /campaigns/{id}, which unambiguously identifies a single-resource fetch. It stops short of explicitly contrasting itself with siblings like emailchef_get_campaign_counts, emailchef_get_campaign_links, or emailchef_list_campaigns, though the field list implicitly distinguishes it.

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?

There is no statement of when to use this tool versus the many campaign siblings. An agent must infer that get_campaign_counts is a narrower fetch and list_campaigns is the bulk variant; the description never routes it. No prerequisites or conditions are given.

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