add_shopping_list_item

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

With no annotations, the description does carry real weight: it discloses that this is a mutating 'Firestore write' and that confirm=true is required, the latter resolving an ambiguity the schema leaves open (confirm is optional with default false). However, it says nothing about permissions, duplicate handling, side effects on the list, or whether the write is reversible.

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?

Two short sentences, front-loaded with the action and followed by the key constraint, with no filler. It is arguably too terse, but nothing present is wasted.

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 5-parameter mutation with zero annotation coverage, the definition is thin: four parameters are unexplained and no preconditions about the target list are given. An output schema exists, so return values need not be described, but the input-side gaps remain significant.

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 description coverage is 0% across 5 parameters. The description only addresses 'confirm'; it adds no meaning for list_id, name, note, or quantity, nor does it explain what confirm actually gates. Given the low coverage, the description should compensate and largely does not.

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 states a specific verb and resource ('Add an item to a shopping list'), which is clearly distinguishable from siblings like complete_shopping_list_item and remove_shopping_list_item. It does not explicitly name those siblings, so it falls short of a 5.

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 only usage guidance is the requirement 'Needs confirm=true', which is useful but is a call precondition rather than a when-to-use-vs-alternatives statement. There is no indication of when an agent should add an item versus completing, removing, or listing items.

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