list_shopping_lists

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

With no annotations, the description only states 'list' which implies read-only, but fails to disclose pagination behavior, ordering, or any side effects. The agent lacks details about what to expect.

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, efficient sentence with no unnecessary words. It is perfectly sized for its simple purpose.

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 description covers the basic purpose but lacks details on return format, pagination behavior, and whether it lists all or only active lists. Given the tool's simplicity and absence of output schema, it is adequate but incomplete.

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% and the description does not explain any parameters (page, per_page). The agent receives no guidance on their meaning or effect beyond default values.

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 'list' and the resource 'shopping lists' with scope 'for the current household', making it distinct from siblings like get_shopping_list (single item) or list_shopping_items (different resource).

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 listing shopping lists but does not provide explicit guidance on when to use it versus alternative tools (e.g., list_shopping_items) or any exclusions.

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