ht_create_shopping_list

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the write-and-safe profile is covered. The description adds a useful behavioral fact — the result is empty — but says nothing about authentication, name uniqueness, or error behavior on duplicate names, which are the remaining unknowns for a create 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, zero padding, and the core action is front-loaded before the teardown pointer. Every clause carries information.

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?

With no output schema, the description should say what creation returns (e.g. a new list identifier needed for subsequent ht_add_to_shopping_list calls) and should explain the required name argument. Those gaps leave an agent without the handles needed to chain calls, though the basic create action is unambiguous.

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% for the single required parameter `name`; only minLength/maxLength constraints exist. The description never mentions that a name must be supplied or what it denotes, so it fails to compensate for the coverage 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 ("Create a new, empty Harris Teeter shopping list") and the word "empty" separates it from ht_add_to_shopping_list, which populates an existing list. It stops short of naming the population tool directly, so differentiation is implied rather than fully stated.

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 second sentence supplies one concrete lifecycle pointer — teardown goes through ht_delete_shopping_list — which implies this tool is for initial list creation. There is no explicit guidance on preconditions (e.g. whether a list must not already exist, or which tool to call next to add items).

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