Get shopping list

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

Annotations already declare readOnlyHint=true, so the description's 'Fetches' is consistent. The description adds value by specifying that items are included (checked and unchecked), which is non-obvious from the tool name alone. However, it does not disclose failure behavior (e.g., invalid list_id), pagination limits, or any other behavioral traits beyond what annotations imply. Given annotation coverage, a score of 3 is appropriate.

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?

A single, well-constructed sentence contains all the essential information with no filler. Every word earns its place, and the structure is front-loaded with the verb and resource.

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 reasonably hints at the return structure ('with all of its items, checked and unchecked'). For a simple fetch tool with only 2 parameters, this is almost complete. It could be slightly improved by clarifying that it returns the full list object including metadata, but the current level is adequate for an AI agent to understand the tool's scope.

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 100%, with both parameters already well-documented in the input schema (list_id as UUID from list_shopping_lists, include_checked with default true). The tool description adds no additional meaning to these parameters. Per the scoring guidelines, baseline 3 is correct when schema fully handles parameter documentation.

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 tool fetches one shopping list with all its items (checked and unchecked). The verb 'Fetches' is specific, and the resource 'one shopping list' distinguishes it from sibling tools like 'list_shopping_lists' (which lists multiple) and mutation tools like 'create_shopping_list' or '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 versus alternatives. It does not mention prerequisites (e.g., needing the list_id from list_shopping_lists), when not to use it (e.g., when bulk listing is needed), or which sibling tool to use instead. The agent is left to infer usage solely from the name and input schema.

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