shopify_fulfillments

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

No annotations are provided, and the description only says 'Get fulfillments', which implies a read operation but does not disclose any behavioral traits such as authentication requirements, rate limits, pagination behavior, or whether it returns all fulfillments for the order. As no annotations exist, the description carries the full burden, but it fails to add value beyond the name.

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 a single sentence, making it concise. However, it is so minimal that it sacrifices necessary detail. It is not verbose, but it lacks structure and completeness for a tool with 4 parameters.

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 tool has 4 parameters (2 required), no output schema, and sibling Shopify tools, the description is incomplete. It does not clarify the return format (likely a list), the need for authentication (implied by parameters but not stated), or the semantics of inputs. The brief description leaves gaps that could confuse the agent.

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 0%, with 4 parameters (shop_domain, order_id, api_key, access_token) lacking descriptions. The description does not explain any parameter (e.g., what shop_domain means, how to provide order_id, or that api_key and access_token are authentication credentials). The agent must rely solely on parameter names, which are ambiguous without context.

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?

Description clearly states 'Get fulfillments for a Shopify order.' The verb 'Get' and resource 'fulfillments' are specific, and together with the context of Shopify orders, it distinguishes from sibling tools like shopify_orders (which deals with orders themselves) and shopify_products.

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 on when to use this tool versus alternatives. Sibling tools like shopify_orders or shopify_products exist, but the description does not specify that this tool is for listing fulfillments associated with a specific order, nor does it mention any prerequisites or constraints.

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