get_ad_stats_csv

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

The description discloses a key behavioral trait: the dry-run mode via confirm parameter, which is important for safe usage. Annotations (readOnlyHint=false, destructiveHint=false) are clarified by this context. No contradictions with annotations.

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 sentence that is concise but omits important details like parameter descriptions. It front-loads the action but could be restructured to include more information without added length.

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 output schema exists, return values are covered. However, the description lacks explanation for input parameters and does not mention potential permissions or size limits for the download. It is minimally adequate but incomplete for a full understanding.

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?

With 0% schema description coverage, the description fails to explain the ad_id and period parameters. Only the confirm parameter is mentioned. The schema already provides types and defaults, but the description adds little semantic value beyond confirming the dry-run logic.

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 provides a specific verb ('Download') and resource ('stats CSV'), clearly indicating the tool's purpose. It is distinct from sibling tools like get_ad_info or list_ads, though it does not explicitly state that this retrieves CSV data for a specific ad.

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 given on when to use this tool versus alternatives (e.g., get_ad_info for single ad stats). The description mentions the dry-run behavior but does not address prerequisites or exclusions.

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