get_campaign_summary

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

No annotations are available, so the description bears full responsibility for behavioral disclosure. It only states 'Get statistics summary' without specifying read-only nature, authentication needs, or what the summary includes. The implicit assumption of a read operation is insufficient.

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 extremely concise (5 words) with no wasted text. It efficiently communicates the core purpose, though at the cost of additional details.

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?

Given the lack of output schema and annotations, the description is too minimal. It does not explain what the summary contains (e.g., total numbers, metrics), making it hard for an agent to decide if this tool meets a specific need without calling it.

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?

The input schema has 100% description coverage for the single parameter campaign_id. The description adds no additional semantic information beyond what the schema already provides, so the baseline score of 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 clearly states the verb 'Get' and the resource 'statistics summary for a campaign'. However, it does not differentiate this summary from sibling tools like get_campaign_bounces, get_campaign_clicks, etc., leaving ambiguity about what specific summary is provided.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., individual campaign stat tools), nor does it mention any prerequisites or context.

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