get_inventory_item

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

No annotations are provided, so the description carries the burden. It clearly characterizes the operation as a read/retrieval and adds useful behavioral detail about scope, such as 'available quantities across all locations.' It does not discuss errors or permissions, but this is a low-risk 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?

The description is compact and front-loaded: it states the action, the lookup keys, and the kind of data returned in two sentences. Every clause contributes useful information with minimal 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 simple retrieval tool with no output schema and no annotations, the description covers purpose, lookup parameters, and return contents well. The main gap is that the need for at least one of id/sku is left implicit despite the schema marking both as optional, but the core invocation path is still clear.

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?

Both parameters are already fully described in the schema with examples, so schema_description_coverage is 100%. The description adds little beyond echoing 'by ID or SKU' and does not clarify whether at least one is required or what happens if both are supplied, but it is not required to compensate for schema gaps.

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 opens with a specific verb and resource: 'retrieves detailed information about a specific inventory item by ID or SKU.' It also enumerates return contents, distinguishing this singular lookup from sibling tools like list_inventory_items.

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 tool's context is clearly implied: use it when you have an ID or SKU and need detailed single-item data. It does not explicitly name alternatives or exclusions, but the 'specific item' wording makes the intended selection reasonably obvious.

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