get_assigned_fulfillment_orders

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

With no annotations, the description carries the full burden. 'Fetch' indicates a read-only operation, but it does not disclose pagination behavior, return format, or any potential side effects. However, for a simple read operation, the description is adequate and does not contradict any annotations (none 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?

The description is a single concise sentence, front-loaded with the verb and resource, and contains no wasted words. It is well-structured for quick scanning.

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?

The tool has no annotations or output schema, so the description is the sole source of behavioral context. It covers the core purpose but omits pagination defaults, filtering options (though in schema), or expected return shape. It is minimally viable but lacks depth for a tool with multiple optional parameters.

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?

The input schema covers 100% of parameter descriptions, so the description adds no additional meaning beyond what the schema already provides. The baseline of 3 applies because the schema is thorough, and the description does not compensate with extra 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?

The description clearly states the action ('Fetch') and the resource ('fulfillment orders') with a specific scope ('assigned to a fulfillment service'). This distinguishes it from sibling tools like get_fulfillment_order (which retrieves a single order) and get_fulfillment_services (which lists services).

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 the tool is for fetching assigned fulfillment orders, which provides clear context for when it should be used. It does not explicitly mention alternatives or exclusions, but the resource scope makes it evident that this is for filtering by assignment status and location, as supported by the parameters.

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