Get Conversion Insights

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

With no annotations available, the description carries the behavioral disclosure burden and adds two useful facts: conversions always equals click_through_conversions, and view-through conversions use a fixed 1-day impression window. However, it does not disclose response shape, pagination, or date-range limits, leaving some 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?

Two sentences with no filler; the action and metrics are front-loaded, and the extra behavioral notes earn their place. Nothing is redundant.

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?

For a simple read-only reporting call the core semantics are present, but with no output schema and no annotations, the absence of any mention of response format or time-range constraints is a noticeable gap. The description is adequate but would benefit from one or two sentences on output structure or filtering behavior.

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 already documents 100% of parameters, establishing a baseline of 3. The description's caveats clarify the returned metrics but do not add parameter-level detail beyond the schema, such as how aggregation_level or entity_ids affect the result.

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 uses a specific verb ('Retrieve') and names the exact resource ('attributed conversion totals') along with the three metric fields returned. It is clear and not a tautology, though it does not explicitly name or contrast sibling tools such as get_delivery_insights.

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 about when to use this tool over alternatives like get_delivery_insights or analyze_campaign_performance. The description focuses on metric semantics rather than providing invocation context, prerequisites, or exclusions.

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