shopify_order_fulfillment_orders

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety/idempotency are covered. The description adds genuinely useful context: that Shopify auto-creates these records and that fulfillment_create operates on them, plus where the location id lives. It doesn't add pagination or rate-limit behavior, but the annotations carry the main burden.

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?

Three short sentences, front-loaded with the core action, with no filler. The pointer to assignedLocation.location.id is a compact, useful addition. Slightly terse on usage, but structurally sound.

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 read-only list tool with full annotation safety coverage and 100% schema coverage, the description is largely complete. With no output schema, pointing to assignedLocation.location.id is a helpful compensating hint about the return structure, though more on the relationship to fulfillment_create's inputs could round it out.

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 100%, so the id and first parameters are fully documented in the schema; baseline 3 applies. The description's mention of assignedLocation.location.id refers to the response shape rather than adding syntax or meaning to the input parameters.

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+resource ('List an order's fulfillment orders') and clarifies what fulfillment orders are ('the first half of fulfilling it'). It distinguishes the concept from ordinary orders, though it doesn't explicitly differentiate why to call this instead of the sibling shopify_order_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?

Usage is implied by 'which is the first half of fulfilling it' and the reference to fulfillment_create naming them, suggesting it's the prerequisite step before fulfilling. However, there is no explicit when-to-use vs when-not or named alternative selection guidance.

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