Create shopping list

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, so the description adds minimal behavioral context. It states 'Creates' (write) and 'in the household', but does not disclose potential side effects, duplicate handling, return behavior, or any authentication/rate limits. Annotations are not contradicted.

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 a single sentence that is front-loaded with the key action and scope. There is no unnecessary verbiage, and it earns its place.

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 create tool with one parameter and no output schema, the description is incomplete. It lacks usage guidelines, parameter explanation, and behavioral details (e.g., return value, side effects). Given many sibling tools (list_shopping_lists, delete_shopping_list, etc.), the agent would need more to correctly invoke this tool.

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%, so the description must explain the 'name' parameter. It does not mention the parameter at all—no syntax, format, uniqueness, or required nature beyond the schema. The description adds zero value for parameter semantics.

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 the verb 'Creates', the resource 'shopping list', and specifies it is 'empty' and 'in the household'. This distinguishes it from sibling tools like list_shopping_lists, get_shopping_list, and add_shopping_list_items.

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 provides no guidance on when to use this tool vs alternatives. It does not mention prerequisites (e.g., name uniqueness) or when not to use it (e.g., if a list with that name already exists). With many related shopping list siblings, such guidance is absent.

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