List shopping lists

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

Annotations already declare 'readOnlyHint: true', so the agent knows this is a safe read operation. The description adds the key behavioral trait that returned data does not include items, which is useful. However, it does not mention pagination behavior or default ordering, which are relevant for a listing tool. The added value is moderate but not rich.

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 of 12 words, front-loaded with the main action. Every word earns its place; there is no redundancy, fluff, or unnecessary information. It is highly concise and well-structured.

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?

The tool has no output schema, so the description should compensate by hinting at what the response contains (e.g., list IDs, names). It does not. For a listing tool, the agent needs to know what fields are returned to use the results effectively. The description is too sparse to be fully complete given the lack of output schema.

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?

Input schema covers 100% of parameters with descriptions, so the baseline is 3. The description does not add any additional meaning beyond what the schema already provides (e.g., 'page' and 'per_page' are already described). No extra param context is given.

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 'lists', the resource 'shopping lists', and the scope 'of the household'. It also explicitly notes what is excluded ('without their items'), which distinguishes it from related tools like 'get_shopping_list' that would include items. This is specific and actionable.

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 obtaining a summary overview of all shopping lists, but it does not explicitly state when to use this vs. alternatives like 'get_shopping_list' (for a single list with items) or 'create_shopping_list'. Some guidance is provided through the exclusion of items, but it is not explicit.

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