Ignore orders

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

Annotations already declare non-read-only, non-destructive, non-idempotent; the description adds the essential behavioral facts: orders are moved rather than deleted, no shipment is created, and the action is reversible via unignore_orders. It doesn't cover edge behavior such as already-ignored or invalid ids, which matters given idempotentHint=false.

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?

Two tight sentences with the core action front-loaded and the follow-up routing appended. Every clause carries information; nothing is padding.

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 single-parameter reversible mutation with no output schema, the definition covers what it does, where orders go, and how to reverse it. The remaining gap is response/error behavior — whether a confirmation or count is returned and how invalid ids are handled — which an agent would otherwise have to discover by calling.

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 the order_ids property already explains its source (list_import_orders). The description adds nothing about batch semantics — the 500-item cap, partial-failure behavior, or what happens with ids already ignored — so it sits at the baseline.

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?

States a specific verb and resource with scope: "Hides store orders from the Import list without shipping them." It also distinguishes itself from the two most confusable siblings by naming list_import_orders (for viewing) and unignore_orders (for reversal).

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?

Gives clear operating context — use this to remove orders from the Import list without creating shipments — and names the sibling used to view the result and the sibling used to undo. It stops short of explicit when-not guidance (e.g. when to delete vs ignore), so not a 5.

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