Campaign analytics: outcomes, sentiment, and what it collected

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

readOnlyHint=true already establishes this is a safe read, so the description is not the sole source of the safety profile. It adds one genuinely useful behavior: csv:true yields a spreadsheet-ready export instead of JSON. It says nothing about pagination, result size, or whether a campaign with no completed calls returns empty.

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?

It is short, but the opening rhetorical question ("Did it work...") costs words without adding information, and the return-field list is packed into a single colon-delimited clause. The operational instruction (csv:true) is buried after the field enumeration instead of being front-loaded.

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 usefully enumerates the returned fields so the agent knows what comes back. Combined with the csv-format note, it covers the essentials for a two-parameter read tool; only campaign-scoping and edge cases are unaddressed.

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%, so the description must compensate for both parameters. It does explain csv:true (spreadsheet export rather than JSON), which is real added meaning, but campaignId is left entirely to inference from its name.

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 and enumerates the returned analytics (per-lead outcome, sentiment, talk time, intent score, collected numbers/names), which separates it from get_campaign and list_campaigns. It is framed as a question plus a field list rather than a clean verb+resource statement, but an agent can tell what it retrieves.

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?

"Did it work, and what did it collect" implies post-campaign outcome analysis, and the csv:true note tells the agent how to switch output format. However, there is no explicit when-to-use vs alternatives guidance and no mention of prerequisites such as the campaign needing to have finished.

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