getConversionReport

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 discloses the default behavior and that the query parameter overrides it, but does not mention other behavioral traits such as rate limits, authentication requirements, or side effects. The read-only nature is implied but not explicit.

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 two concise sentences with no fluff. The first sentence states the primary purpose and default, and the second explains the override capability. Every word earns its place.

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?

Given the lack of output schema and annotations, the description adequately covers the tool's functionality, including default behavior and custom queries. However, it could be more complete by mentioning potential limitations or providing example outputs, though the rules note that output schema is not required.

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%, and the description adds value by explaining the default behavior and providing examples for the query parameter ('e.g. session/conversion-funnel queries'). This extra context helps the agent understand how to use the parameters effectively beyond the schema definitions.

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 it provides product performance via ShopifyQL, with a default of top 25 products by total_sales over a date range, and the ability to override with a raw query. This distinguishes it from sibling tools like runShopifyQL (which executes raw queries without defaults) and other report tools.

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 explains the default behavior and how to override with a raw query, providing clear context for when to use the tool. However, it does not explicitly state when not to use it or mention alternatives, which could be improved.

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