add_inventory_item

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

With no annotations, the description carries the full burden. It discloses key side effects (auto-creation of brand/part type/location/vendor) and parameter-specific behaviors (low stock tracking only for consumables). This is substantial behavioral context, though it omits details like error handling or return behavior.

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 well-structured with a brief intro followed by a compact Args list. Every line adds value, and the length is appropriate given the parameter count.

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 complexity of a 12-parameter create operation with no annotations, the description is remarkably complete. It covers action, side effects, and all parameters, while relying on the output schema for return format. It doesn't discuss permissions, but that's a minor gap.

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?

All 12 parameters are explained in the Args section, providing semantics beyond the schema's bare names. For example, 'is_consumable' clarifies it enables low stock tracking, and 'low_stock_threshold' is specified as consumables-only. This fully compensates for the 0% schema description coverage.

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 clearly identifies the operation as adding a new inventory item with a specific verb and resource. It does not explicitly differentiate from sibling update/search tools, but the action is unambiguous.

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 establishes clear context for creating a new inventory item and notes that related entities are auto-created, which informs decision-making. It does not explicitly name alternatives or exclusion criteria, such as using update_inventory_item for existing items.

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