bring_smart_add

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

No annotations exist, so the description carries the full burden and does disclose real behavior beyond the schema: per-item routing to store lists via store_mappings.json, and that unmapped items are reported back rather than silently dropped. It stops short of covering duplicates, partial failures, or auth requirements for a mutation tool.

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?

Four short sentences, front-loaded with what the tool does and ending with the routing decision rule. There is mild redundancy between 'based on stored store preferences' and 'based on store_mappings.json', which restate the same mechanism twice.

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 single-parameter batch tool with no output schema, the description covers the essential unknowns: the routing source, the store examples, and the fate of unmapped items. Return-shape details are partially implied ('reported back'), which is adequate but not exhaustive.

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?

Only one parameter and the schema already documents it at 100% coverage, including the nested name/specification fields. The description adds the batch-routing context ('each item is routed to its mapped store list') but no syntax or format detail beyond the schema, so the baseline 3 applies.

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+resource (smart-add items to Bring! shopping lists) and immediately names the mechanism (store_mappings.json routing). It explicitly contrasts itself with the sibling bring_add_item, so an agent can separate the two without opening either schema.

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?

Gives an explicit selection rule: 'Use this instead of bring_add_item when you don't know which list an item belongs to.' That is a named alternative plus the condition that selects it, at the top end of the scale.

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