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

Annotations already mark the tool as destructive and non-idempotent, and the description reinforces this by stating that repeating removes stock again and that the action cannot be undone except by adding stock back. It stops short of describing permissions or rate limits, but adds meaningful consequence detail beyond the structured hints.

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 tightly front-loaded with the write operation and key caveats, then ends with the endpoint. Every sentence adds useful information without repetition or waste.

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 inventory mutation, the description covers the essential behavioral risks: non-idempotence, irreversible stock reduction, and the only in-server recovery path. It does not address the optional parameters or permissions, but the annotations and schema cover enough that the definition is largely complete.

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 already describes the three required IDs and the adjustment quantity, but three optional parameters (date, lot_number, description) lack schema descriptions. The tool description does not compensate by explaining those fields or adding meaning beyond the existing parameter documentation.

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 states a specific verb and resource: taking stock out of an inventory item in a storage location. It explicitly labels the operation as a WRITE and names the endpoint, making it clearly distinguishable from add/read inventory siblings.

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 gives concrete usage contexts (use, loss, sale) and explains the consequence of repeating the call. It does not explicitly name the alternative tool for adding stock back, but the implication is clear enough for an agent to infer the inverse operation.

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