households_shopping_lists_get_all

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

With no annotations, the description must disclose behavioral traits, but it does not. It fails to mention that the tool is read-only, supports pagination, or any other behavior. The presence of pagination parameters in the schema is not reflected in the description.

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 very short, but it is under-specified to the point of being unhelpful. Conciseness should not come at the cost of clarity. Adding essential information would improve it without making it verbose.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description is completely inadequate. It does not explain the return format, pagination behavior, or filtering options, leaving a large knowledge gap for the agent.

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 adds no insight into the parameters. It does not explain the purpose of page, perPage, orderBy, or other parameters, leaving the agent to rely solely on parameter names which may be ambiguous.

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 says only 'Get All', which is vague and does not specify what resource is being retrieved. The endpoint path in square brackets indicates it's for shopping lists, but the description itself lacks this clarity, making it difficult to distinguish from other 'get_all' tools.

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?

No guidance is provided on when to use this tool versus alternatives, such as 'households_shopping_lists_get_one' or other list retrieval tools. The description gives no context about prerequisites, typical use cases, or limitations.

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