remove_shopping_list_item

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

With no annotations, the description carries the full behavioral burden; it does disclose that this is a mutating Firestore write and that a confirm flag must be set true, which is a meaningful safety gate beyond nothing. It omits reversibility, required permissions/ownership, and error behavior for missing items, leaving substantial gaps for a destructive 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?

Two short sentences, with the core action front-loaded and the required precondition immediately after. No filler or redundant restatement of the tool name.

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 single-item deletion with an output schema present, the description covers the essential action and the confirm requirement. It is only slightly thin on failure modes and ownership preconditions, which are low-risk given the tool's narrow scope.

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 three parameters, so the description must compensate. It adds real meaning for 'confirm' (must be true, overriding the schema default of false) but says nothing about list_id or item_id beyond their self-evident names, leaving a partial gap.

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?

States a specific verb and resource ('Delete a shopping-list item'), which cleanly separates it from siblings like add_shopping_list_item, complete_shopping_list_item, and shopping_list_items. It stops short of naming those siblings explicitly, so an agent must infer the boundary from the verb alone.

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 'Needs confirm=true' clause gives a precondition for invocation, which implies usage. However, there is no guidance on when to prefer removal over complete_shopping_list_item, nor any note about what happens if the item or list does not exist.

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