get_items

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

With no annotations, the description carries the full burden and does well: it discloses result ordering (unchecked first, then checked), the exact row format including itemId, and that several rows can share a name. It falls short of a 5 because it never explicitly states the tool is read-only with no side effects, nor how it behaves for an empty or missing list.

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?

It is front-loaded with purpose, then result format, then usage rules, and nearly every sentence earns its place. It is somewhat sprawling, mixing output format, duplicate-name handling, and multi-row editing policy into one block, which keeps it just short of 5.

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?

There is no output schema and no annotations, so the description must explain return values and behavior — and it does, covering ordering, row format, itemIds, and duplicate-name semantics. For a two-parameter read tool, an agent has everything needed to call it and interpret the result.

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 coverage is 100%, so listId and listName are already fully documented, including that listName is shown in the permission prompt and not sent to the API. The description adds no semantic detail about the parameters themselves, so the baseline 3 is appropriate.

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 ('Get every item on one list') and immediately distinguishes this tool's scope from list-level siblings by describing the per-item result. An agent can tell exactly what it retrieves without opening the 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 explicit when-to-use rules: call before edit_items/delete_items to obtain itemIds, before add_items to avoid duplicates, report only unchecked items when asked what to buy, and ask which row when several match. It names sibling tools and the conditions that select them, leaving little to inference.

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