shopify_list_refunds

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

With no annotations, the description carries full behavioral burden. It only states 'list recent order refunds' but lacks details on auth requirements, rate limits, pagination, or the meaning of 'recent'. This is minimal transparency for an agent needing to decide invocation.

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 concise with two short sections. It front-loads the purpose, but could be more structured with explicit labels or bullet points for clarity.

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 tool with output schema, the description is mostly adequate. However, it lacks definition of 'recent' and does not mention the default limit (50 from schema). These gaps reduce completeness for agent decision-making.

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 description adds value beyond the schema by specifying the limit range (1-250) and clarifying order_id as optional for scoping. Given 0% schema description coverage, this is helpful, though it could include default limit and format details.

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 lists recent order refunds in the shop, including the verb 'List' and the specific resource 'order refunds'. However, 'recent' is ambiguous and no differentiation from sibling list tools is provided.

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 on when to use this tool versus alternatives like shopify_list_transactions or other list tools. The description does not include when-not-to-use or explicit context for usage.

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