Order Fulfillments Delete

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

The annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so the broad safety profile is known. The description adds valuable auth context ('Required scope: write_shipping') and the exact HTTP endpoint, but it does not say what is destroyed, whether the deletion is reversible, or what happens to related records. It is useful but not rich.

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 front-loaded with the action and resource, followed by the endpoint, scope, and API version on separate lines. Every line earns its place for an API-gateway-style tool. It is slightly terse but not padded.

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 destructive mutation with a complete two-parameter schema and rich annotations, the description covers endpoint, scope, and API version. It still omits the expected success response (e.g., 204/no content) and any note on irreversibility or side effects, which an agent invoking a destructive delete would benefit from knowing.

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% and both parameters have descriptions, so the schema already carries the semantic load for order_id and id. The path template in the description reinforces how those values are used, but adds no format, type, or constraint detail beyond what the schema provides. Baseline 3 is appropriate.

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 gives a specific verb and resource: 'Delete a legacy fulfillment event.' The word 'legacy' helps distinguish it from the sibling family around fulfillment_orders, though it never names the non-legacy alternative explicitly. An agent can still tell what the tool does without opening the schema.

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 adjective 'legacy' implies this should be used only for legacy fulfillment events, and the required scope 'write_shipping' signals the permission gate. However, there is no explicit when-to-use versus the sibling tiendanube_fulfillment_orders_delete, and no prerequisites or exclusions are stated. Usage is inferred rather than guided.

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