adjust_inventory

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

No annotations provided. Description explains mutation effect but does not disclose edge cases (e.g., negative inventory handling), permissions, or reversibility. Basic transparency but could be more comprehensive.

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 sentences, no extraneous information. Front-loaded with action and key constraints. Every sentence earns its place.

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?

Adequate for a simple mutation tool with 3 parameters and no output schema. Explains purpose, parameters, and prerequisites. Could mention expected return but not necessary.

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%, but description adds value by summarizing adjustment direction ('positive to add') and source of inventory_item_id. Enhances understanding beyond raw schema.

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?

Description clearly states it adjusts inventory by a relative amount, with explicit positive/negative semantics. It identifies required IDs and distinguishes from siblings like set_inventory (absolute) and list_inventory_levels (read).

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: requires inventory_item_id and location_id. Implies when to use (adjusting stock relatively) but does not explicitly exclude alternatives like set_inventory for absolute adjustments.

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