asc_get_geo_conversion_summary

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

With no annotations, the description discloses default daysBack and handling of missing data. However, it does not mention idempotency, read-only nature, or any side effects. Adequate but not comprehensive.

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?

Three concise sentences with no wasted words. Front-loaded with purpose, then usage, then behavior. Perfectly sized.

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?

Describes output format partially but omits details like whether data is cumulative or per-day, how conversionRate is calculated, or pagination. Adequate for simple tool but could be more complete given no output schema.

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?

Only daysBack is explained (default 7 days). minTrials is not described at all despite 0% schema description coverage. The description partially compensates for one parameter but fully misses the other.

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 the tool aggregates SUBSCRIPTION_EVENT data by country and SKU, listing the returned fields. It distinguishes from sibling tools that likely return raw events (e.g., asc_get_subscription_events).

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?

Explicitly states to use this for comparing geo/pricing performance across paid campaigns. Does not include explicit exclusions, but the purpose and context with siblings imply when not to use (raw events).

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