Seller mark shipped

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

Beyond the annotations, the description discloses idempotent no-op behavior and the automatic enqueueing of carrier polling. It does not exhaustively describe all side effects, but the annotations already cover read-only/destructive hints, so the additional context is valuable.

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 concise, front-loaded with the primary action, and contains no filler. The idempotency and side-effect details are included in two tight sentences.

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 description covers the primary purpose, idempotency, and a key side effect, while the schema supplies required parameters and constraints. It does not mention error conditions or return values, but these are not essential for a basic call.

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 schema provides full descriptions for all parameters, including a clear explanation of the tracking_number idempotency. The tool description adds little beyond what is already present in the parameter schemas.

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 'Mark an order as shipped with a tracking number,' which is a specific action and distinguishes it from related tools like seller_mark_delivered or seller_attach_tracking. The scope is immediately understandable.

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 explains the core behavior and idempotency, but it does not explicitly say when to use this tool over alternatives such as seller_mark_delivered or seller_attach_tracking. Usage context is implied but not directly stated.

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