get_lists

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

With no annotations provided, the description carries the full burden. It transparently discloses that the tool returns all lists on the account (scope) and the specific return fields (uuid and name), which is sufficient behavioral context for a read-only listing operation. It does not overstate side effects, and no contradictions exist.

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, front-loaded sentence with no filler. Every phrase ('every', 'on the account', 'with its uuid and name') adds specification and 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 zero-parameter operation with an output schema present, this description provides the essential information: the action, the resource scope, and the returned fields. It lacks nothing needed for correct invocation.

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?

The input schema already covers 100% of parameters (zero parameters), so there is nothing to add from the description. The description focuses on output fields rather than inputs, which is appropriate. Baseline 4 for a zero-parameter tool.

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 ('List'), a precise resource ('every Bring! shopping list on the account'), and the included fields ('uuid and name'). This clearly distinguishes it from item-focused siblings like get_list_items, add_item, remove_item, and complete_item.

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 implies the tool is for retrieving the full set of shopping lists at the account level, but it does not explicitly state when to use this tool instead of the item-focused siblings. There is no exclusion or alternative guidance, so the agent must infer usage from tool names.

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