Add an item

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

Annotations already declare this is a non-read-only, non-destructive write, so the safety profile is covered. The description adds real behavioral context beyond them: new tag names are created implicitly, collectionId seeds fields from a template, wanted items are excluded from totals/report/stock/search, and the new item with its id is returned. It stops short of error/failure behavior or what happens on a duplicate name.

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?

Front-loaded with the core action and the dedup rule, then grouped by concern (placement, categorization, pricing, collection/wanted, photo path, return value). It is dense and semi-colon heavy, but nearly every clause carries a distinct decision-relevant fact; a small amount of parenthetical tool-name repetition could be trimmed.

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 31-parameter creation tool with no output schema this covers what an agent most needs: the one required field, dedup avoidance, the id-lookup prerequisites, the wanted/owned lifecycle, and a stated return value. Remaining gaps are minor because the schema itself documents the long-tail fields (serialNumber, disposition, purchaseDate) thoroughly.

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% and each parameter already carries a rich description, so the baseline is 3. The description does add routing value the schema lacks — telling the agent which sibling tool to call to obtain locationId, categoryId, collectionId and tag context, and reinforcing that prices are in cents and that new tags are auto-created — but it does not explain most of the 31 parameters itself.

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?

Opens with a specific verb+resource ('Adds a new item') and immediately frames it against siblings (search_inventory, update_item, adjust_stock, add_item_from_photo). An agent can tell exactly which of the ~39 tools this is and which it is not.

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?

Explicit when-to-use logic with named alternatives: search first to avoid duplicates, update_item/adjust_stock if it exists, add_item_from_photo for photo origin. Also states the wanted:true → update_item with wanted:false lifecycle, which is a non-obvious workflow rule.

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