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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the metric inventory, effectively disclosing the return payload in the absence of an output schema, but says nothing about the reporting window, whether figures are cumulative or time-bounded, or how fresh the data is — the one behavioral trait that matters most for a report tool.

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 compact sentence that front-loads the scope word 'Campaign report:' and then lists payload fields; nothing is redundant. It loses a point for being a verbless fragment whose metric terms ('released', 'human', 'machine') are domain jargon not glossed anywhere.

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?

As a read-only tool with two fully documented parameters and no output schema, the metric enumeration does much of the work an output schema would. Still missing is any statement of time window/aggregation and any differentiation from nearby report and live-view siblings, which leaves a real ambiguity for an agent choosing among them.

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 100% for both parameters, and the purpose parameter carries substantial inline guidance, so the baseline is 3. The description itself contributes nothing about campaign_id or purpose, adding no meaning beyond the schema.

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 names the resource (a dialer campaign report) and enumerates the exact metrics it returns — released, answered, human, machine, no answer, busy, failed, outcomes, budget, cost split, cost per connect — so an agent knows quite precisely what data it gets. It is a noun phrase with no verb and never explicitly contrasts with get_dialer_live, get_dialer_campaign or get_call_stats, so distinction from siblings is left to inference.

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 when-to-use statement, no exclusion or alternative named, and no mention of prerequisites (e.g. whether the campaign must have run or be active). The only guidance an agent can infer is that this is a reporting read on a campaign rather than a live view.

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