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

The annotations already indicate this is a non-read-only, destructive, idempotent mutation. The description aligns with those annotations and adds concrete behavioral details about status and tracking updates. No contradiction exists.

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 redundant, including separate sentences for tracking URL and tracking number, and it contains an awkward truncated 'Guidance:' section that repeats earlier content. This hurts clarity and conciseness.

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?

Given the annotations and full schema coverage, the description provides enough context for an agent to use the tool correctly. It explains the allowed transitions and the fields involved; no output schema is present, so return-value details are not required.

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 description adds meaningful context by explaining the status transition rules and the role of tracking fields. It doesn't restate every schema detail, but it supplements them effectively.

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 that the tool sets the shipping status of an order to the passed value and also updates tracking number and URL. The resource and action are specific, and the title reinforces the purpose.

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?

It explicitly explains the allowed status transitions (PENDING to FULFILLED, FULFILLED to DELIVERED), which is important usage guidance. It does not compare directly to sibling update tools, but the constraints are clear enough for when this tool should be used.

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