list_fulfillments_for_order

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

With no annotations, the description carries the full burden. It discloses the return content (tracking info, line_items, delivery status), which is valuable behavioral info. However, it omits potential caveats like pagination, ordering, or filtering behavior, so it provides only moderate transparency for a list operation.

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 extremely concise: two sentences, front-loaded with the core purpose, and no extraneous information. Every word earns its place.

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 one-parameter list tool without an output schema, the description covers the essential return details and required input. It lacks any mention of pagination or potential edge cases, preventing a perfect score, but it is sufficiently complete for basic agent use.

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 coverage is 100% with order_id fully described in the schema. The description adds no additional parameter semantics beyond what the schema already states. Baseline of 3 is appropriate because the schema does the heavy lifting.

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 action and resource: 'List all fulfillments for a specific order' uses a specific verb and object. It distinguishes from siblings like get_fulfillment (single fulfillment) and create_fulfillment (write) by emphasizing 'all fulfillments' scoped to a specific order.

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 the phrase 'for a specific order' but does not explicitly contrast with get_fulfillment or other sibling tools. No clear exclusions or when-not-to-use guidance is provided, making the usage guidance merely implied rather than explicit.

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