adjustInventory

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

With no annotations, the description carries full burden but fails to disclose behavioral traits beyond the verb 'adjust'. It does not specify whether the quantity is set absolutely or delta-adjusted, what side effects occur (e.g., reservations), authentication needs, or reversibility. For a mutation tool, this is insufficient.

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 extremely concise at three words, which is efficient but at the cost of necessary detail. It could be slightly longer to include critical context without becoming verbose, so it is minimally acceptable.

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?

Given the tool has three required parameters, no output schema, and no annotations, the description is incomplete. It does not explain what 'adjust' means (e.g., additive or absolute), response format, or error conditions, leaving significant gaps for an agent.

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% (no parameter descriptions) and the tool's description does not elaborate on any of the three parameters: inventoryItemId, locationId, or quantity. The description adds no meaning beyond the raw schema, so the agent lacks guidance on valid values or units.

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 'Adjust inventory quantity' clearly conveys a mutation verb and resource, distinguishing it from read-only siblings like getInventoryLevels. However, the term 'adjust' is somewhat vague (e.g., relative vs absolute change), and no sibling tool performs the same function, so clarity is good but not excellent.

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?

No guidance is provided on when to use this tool versus alternatives, prerequisites, or exclusions. The description simply states the action without any usage context, leaving the agent to infer conditions such as requiring an inventory item and location.

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