generate_campaign_report

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

The description discloses that the tool can use live data or a deterministic demo mode, which is a behavioral trait. However, with no annotations, it fails to disclose other important aspects like permissions, side effects, or rate limits.

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, front-loaded sentence that efficiently conveys the core action. It is concise, though it could briefly describe parameters without losing brevity.

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 complexity (6 parameters, nested objects, enums), the description is too sparse. It does not explain demo mode, report formats, or group_by behavior. Output schema exists but does not justify the lack of parameter context.

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 0% description coverage and the tool description provides no explanations for any of the 6 parameters, including required ones like campaign_ids, date_range, and metrics. This forces the agent to infer meaning from schemas alone.

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 tool generates campaign performance reports and distinguishes it from siblings by specifying data sources (live vs demo mode). The verb 'generate' and resource 'campaign performance reports' are specific and unambiguous.

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 guidance is provided on when to use this tool vs alternatives like analyze_audience_segments. There is no mention of prerequisites or exclusion criteria.

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