get_campaign_report

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

No annotations provided, so description carries burden. Discloses side effect: 'writes an HTML version with interactive charts.' Does not mention other traits like latency or permissions, but sufficient for a read-like operation.

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?

Two sentences: first states purpose, second enumerates contents and side effect. No filler.

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?

Lists multiple report sections and side effect; output schema exists. Lacks guidance on error handling if campaign not run, but overall sufficient.

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 has 100% coverage for one parameter. Description adds context that campaign must have been previously executed with 'run_campaign,' but this is minimal extra over schema description.

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?

Clear verb+resource: 'Generate the pre-flight report for a campaign that has been run.' Lists specific components (funnel, segment breakdown, etc.), distinguishing from siblings like 'report' or 'compare_campaign_variants'.

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?

States it's for a campaign that has been run; parameter description reinforces execution with 'run_campaign.' Does not explicitly exclude unrun campaigns or compare with siblings.

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