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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's real contribution is the disclosed side effect: 'Delivered restocks the linked supplement.' That is exactly the mutation consequence an agent needs before calling. It stops short of saying whether prior status matters or how the restock quantity is determined.

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 short sentences, zero filler, and the side-effect warning is placed immediately after the action statement rather than buried. Nothing is repeated from the schema.

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 no output schema, the description covers the main side effect but omits how totalUnits interacts with the status transition and what happens to supplement inventory if it is omitted. An agent could call this correctly but might restock with a wrong implied pack size.

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 67% and the status enum is already fully documented in the schema. The description clarifies the consequence of the 'delivered' value but never mentions totalUnits, that it is optional, or that it is only meaningful in the delivered case — a meaningful gap given it resets inventory.

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 ('Set') and resource ('shopping-list item's status') and enumerates the only two valid target states. It does not name or differentiate itself from the sibling stackwell_update_shopping_item, so an agent must infer which one to pick.

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?

Usage is only implied: an agent can guess 'ordered' is set on purchase and 'delivered' on receipt, but there is no explicit when-to-use guidance, no prerequisites, and no routing versus the closely named stackwell_update_shopping_item sibling.

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