get_campaign_analytics_overview

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states this is a 'Get' operation, implying read-only behavior, but doesn't address important aspects like authentication requirements, rate limits, error conditions, or what format the 'analytics overview' returns. For a tool with no annotation coverage, this leaves significant behavioral gaps.

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, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple retrieval tool and front-loads the essential information.

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 annotations and output schema, the description should provide more context about what this tool actually returns and how it differs from sibling analytics tools. The current description is too minimal for a tool that presumably returns analytics data - it doesn't indicate what metrics are included in the 'overview' or what format the results take.

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 schema description coverage is 100%, with both parameters ('start_date' and 'end_date') clearly documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the schema, but since the schema provides complete coverage, the baseline score of 3 is appropriate.

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 'Get analytics overview for all campaigns' clearly states the verb ('Get') and resource ('analytics overview for all campaigns'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'get_campaign_analytics' or 'get_warmup_analytics', which appear to offer related analytics functionality.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'get_campaign_analytics' and 'get_warmup_analytics' available, there's no indication of what differentiates this 'overview' tool from other analytics tools, nor any mention of prerequisites or context for its use.

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