get_earnings_by_ad_format

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

With no annotations provided, the description carries the burden. It implicitly indicates a read-only operation via 'Get', but does not explicitly state read-only behavior, permissions, or any limitations. It adds the insight about 'most revenue' but lacks explicit behavioral disclosure.

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 short sentences, front-loaded with the core purpose. No wasted words; the second sentence adds a useful usage angle without repetition.

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?

With 3 simple parameters and no output schema, the description adequately explains the tool's function. It could mention what the response contains, but the phrase 'Shows which ad formats generate the most revenue' implies the output structure. Overall sufficient for a simple listing tool.

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 description coverage is 100%: all parameters are described in the schema, including the enum values and date format. The description adds no parameter-specific semantics beyond the schema, so a baseline of 3 applies.

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?

Description clearly states a specific verb 'Get earnings breakdown' with resource 'ad format' and examples (In-page, Anchor, Vignette), distinguishing it from sibling breakdown tools like get_country_breakdown and get_platform_breakdown.

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 analyzing revenue by ad format via 'Shows which ad formats generate the most revenue', but it does not explicitly name alternatives or state when not to use it. Since the tool is one of several breakdown tools, a more explicit distinction would help, but the context is clear.

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