Remove Inventory

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't bear a heavy burden. It adds that the record must be 'existing' and that adjustmentReasonName must match a configured reason, but doesn't detail side effects (e.g., exceeding quantity, permissions). No contradictions.

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?

Description is compact, front-loaded with a clear purpose, followed by structured Args and Returns. No filler.

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 operation, it explains how to identify the record, what parameters are needed, and what it returns. However, it doesn't describe error conditions or edge cases (e.g., removing more than available), and the return is vaguely 'operation result from Logiwa' with no output schema.

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 has 100% coverage, so baseline 3. The description adds extra value by specifying that inventoryIdentifier comes from logiwa_list_inventory and that adjustmentReasonName must match a configured reason, which goes beyond the schema descriptions. The Args section mirrors schema but with useful operational context.

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 states the operation: decreases quantity units from an existing inventory record. Uses specific verb 'Decreases (removes)' and resource 'inventory record', and distinguishes from siblings like add_inventory and adjust_inventory by specifying removal.

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?

Provides clear context: identify the record via inventoryIdentifier from logiwa_list_inventory. It implies this tool is for removing inventory, but doesn't explicitly contrast with adjust_inventory or transfer_inventory, nor state when not to use.

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