adjust_inventory

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

With no annotations, description discloses the destructive side effect (mutates live store), exact overwrite semantics, idempotency key, and 204 normalization to {}, which goes well beyond structured data.

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?

Four tight sentences, front-loaded with the critical mutation warning; every sentence adds operational value (set semantics, idempotency, return normalization, usage caveat).

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 two-param mutation with no annotations but an output schema, the description covers side effects, input semantics, return behavior, and usage condition—everything an agent needs to decide and invoke safely. The output schema supplies return details, so no duplication.

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 0%, but description adds semantic meaning to both parameters: variant_id is the stock target and quantity is exact finite target value, explicitly a set not a delta. This fully compensates for schema's lack of descriptions.

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?

Clearly identifies as a mutation to set a variant's stock to a concrete quantity, using specific verb 'set' and resource 'variant's stock'; distinguishes from sibling read-only inventory tools by emphasizing live store mutation and set-not-delta. No ambiguity.

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?

Explicitly warns 'Use only when you intend to change real inventory' and states MUTATES THE LIVE STORE, giving clear context for when to invoke. It does not explicitly name alternative tools or exclusions, but this is sufficient guidance among inventory/order siblings.

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