Fulfillment Orders List

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior. The description adds meaningful context beyond those annotations by disclosing the HTTP endpoint, required OAuth scope, API version, and the response envelope, though it does not discuss rate limits or pagination behavior beyond the response fields.

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 compact and front-loaded, with the main purpose stated first followed by endpoint, scope, version, and return shape. Every line adds practical information without unnecessary prose.

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 operation, the description covers the essential context: endpoint, required scope, API version, and response structure. With no output schema, the included return shape is especially valuable, and the annotations plus full parameter schema cover the remaining gaps.

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 input schema already documents page, fields, order_id, per_page, and response_format in detail. The description only restates the endpoint's order_id path variable and does not add syntax or usage guidance beyond what the schema provides.

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 a specific verb and resource: list fulfillment orders of an order. It adds useful domain context by noting this is the modern way to manage packing, dispatch, and tracking, but it does not explicitly differentiate itself from nearby siblings such as tiendanube_order_fulfillments_list.

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 implies usage through 'modern way to manage packing, dispatch and tracking,' giving some context for when this tool is relevant. However, it does not state when to use this instead of alternatives like order fulfillments list/get, nor does it mention exclusions or prerequisites beyond the required scope.

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