create_shopping_item

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool creates an item and outlines two modes, but lacks details on side effects, authorization, error behavior, or output structure (though an output schema exists). Some behavioral context is given but not comprehensive.

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: two short sentences after the initial purpose statement. Every sentence adds value, with no redundancy or fluff. It front-loads the purpose and immediately provides actionable mode guidance.

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's complexity (7 parameters, 1 required) and availability of an output schema, the description covers the main usage patterns but misses explaining the required 'list_id' parameter and the return value. It is adequate but not fully comprehensive.

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?

With 0% schema description coverage, the description must compensate. It explains 'note', 'is_food', 'food_id', and 'unit_id' with examples, but omits 'list_id' (required), 'quantity', and 'label_id'. It adds value for some parameters but leaves others undocumented.

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 states 'Create a single shopping item on a list,' with specific verb and resource. It distinguishes from sibling 'create_shopping_items_bulk' by emphasizing 'single' and provides two distinct usage modes (free-form vs structured).

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 offers guidance on when to use free-form vs structured items, but does not explicitly contrast with alternative tools like 'create_shopping_items_bulk' or mention prerequisites (e.g., list must exist). Usage is implied but not fully explicit.

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