shopify_mark_order_paid

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 mentions that the operation marks an order as paid and returns an updated order plus userErrors, but does not disclose idempotency, mutability, or what happens if the order is already paid or does not exist.

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?

Two concise sentences with no redundancies. The first sentence states the action and API name; the second provides use case and return information. All content is essential and well-structured.

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?

Despite no output schema, the description adequately covers the tool's action, intended use, and return values (updated order + userErrors). For a single-parameter tool, this is fairly complete, though it could include error handling details.

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?

With 0% schema description coverage, the description must explain parameters. It does not elaborate on the 'id' parameter beyond its existence, leaving the agent to infer that it is the order ID. This lack of explicit clarification is a significant gap.

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's action (mark an order as paid), the API function name, and the specific use case (offline payments captured outside Shopify). It distinguishes itself from siblings by focusing on a unique payment operation not covered by other 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 explicitly states when to use the tool (offline payments where funds were captured outside Shopify). It implicitly excludes online payments, but does not name alternative tools or explicitly state when not to use it.

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