get_inventory_item

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

With no annotations, the description carries the burden. It discloses that the tool returns warehouse stock quantities, which is useful. However, it does not mention failure modes (e.g., not found), access permissions, or whether the item might be a non-stock item. This is minimal but acceptable for a simple read operation.

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?

A single clear sentence with no filler. It front-loads the action and resource, and every word adds value.

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 tool with one parameter, this description is fairly complete: it states what is returned (item with warehouse stock quantities). It lacks explicit alternates or edge-case behavior, but given the simplicity, the coverage is good. An output schema does not exist, so the description provides the only return info.

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%: the schema already documents inventoryID as 'Inventory item ID / item code'. The description adds no further parameter semantics, so the baseline of 3 applies.

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 uses a specific verb ('Get') with a precise resource ('specific Acumatica inventory item') and adds a key detail (warehouse stock quantities). This clearly distinguishes it from siblings like list_inventory_items, which would fetch multiple items, and other get_* tools.

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?

The description implies use when you need a single, specific inventory item because it says 'specific' and the schema requires an inventoryID. However, it does not explicitly state when to prefer this over list_inventory_items or any other alternative, nor does it mention any prerequisites or exclusions.

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