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

No annotations are provided, so the description carries the full burden. It usefully discloses a prerequisite (market sync must have run at least once) and the order-attribution logic (Shopify market field for Plus, country-code fallback otherwise), which are non-obvious caveats. It leaves out rate limits or output-shape details, but the disclosed caveats are valuable.

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?

Purpose and report contents are front-loaded before the usage and caveat notes, with a logical flow. It is a single dense paragraph; the caveat sentence is longer than strictly needed but still earms its place by flagging a real prerequisite.

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?

No output schema exists, and the description adequately covers what each report returns plus the sync prerequisite. Pagination is handled by the schema's _offset description, so nothing critical is missing for correct invocation, though attribution caveats could be elaborated slightly.

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 coverage is 100%, so baseline is 3, but the description enriches the 'report' enum beyond the schema by specifying that performance includes revenue, orders, AOV, and revenue share, not just 'revenue by market'. It confirms date-range semantics that the schema already documents.

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?

States a specific verb and resource ('Get Shopify Markets data') and enumerates exactly the two reports it returns: market definitions (countries/currencies) and per-market revenue performance. An agent can immediately tell this is the geographic-market tool, distinct from the marketing/campaign-oriented siblings.

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?

Gives clear context: 'Use this to understand which geographic markets are configured and how revenue is distributed across them.' This tells the agent when the tool applies, though it names no alternatives or when-not conditions relative to the many sibling reporting tools.

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