snapchat_get_account_report

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

Annotations already confirm read-only and non-destructive behavior. The description adds valuable behavioral details: uses 2 API calls, falls back to concurrent calls on error, and caches results for 5 minutes. No contradictions.

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?

Four sentences, each adding distinct value: purpose, efficiency, fallback, caching. Front-loaded with the core function. No redundant or fluff sentences.

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?

Covers purpose, efficiency, fallback, and caching. With output schema present and good parameter descriptions, the description is nearly complete. Could mention comparison to siblings for full completeness.

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 detailed descriptions for each property within StatsInput, so the schema carries the burden. The description does not add parameter-level meaning beyond what the schema provides, earning a baseline score of 3.

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 'Full account-level performance report with per-campaign breakdown', using a specific verb ('get') and resource ('account report'). It distinguishes from sibling tools like snapchat_get_performance_stats which target individual entities.

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?

The description implies usage for broad account reporting but does not explicitly mention when to use this tool versus alternatives like snapchat_get_performance_stats. No when-not or exclusion criteria are provided.

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