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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only 'currency-aware' and 'coverage', neither of which explains behavior such as multi-currency handling, what coverage means, or how date ranges and intervals interact.

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 sentence, but it is under-specified rather than concise. For a tool with 10 parameters and multiple enums, the front-loaded content is too sparse to guide effective invocation.

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?

This is a complex read tool with 10 parameters, no output schema, and no parameter descriptions. The description does not fill the resulting gaps, leaving the agent without enough context to choose the right period, source, interval, breakdown, currency, or comparison options.

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 0% across 10 parameters, so the description carries the full burden of explaining parameter semantics. It only vaguely hints at currency handling via 'currency-aware', and does not clarify period, date range, source, interval, breakdown, comparison, or Shopify connection behavior.

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 has a verb ('Read') and resource ('sales'), so the basic purpose is inferable. However, 'with coverage' is vague and does not clarify what is being covered, and there is no differentiation from related siblings such as orders_get, analytics_query, or funnels_analytics_get.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The agent is left to infer usage entirely from the name and terse phrase.

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