get_shopping_lists

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

No annotations are provided, so the description carries the full burden. It discloses the scope of the result ('todas las listas del hogar') which is useful context, but says nothing about read-only nature, permissions, pagination, or behavior when the household has no lists.

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 front-loaded sentence with no filler. It is appropriately sized, though being one clause it cannot carry much structure.

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?

An output schema exists, so return-value explanation is not required, and there are no parameters to document. However, for a tool with no annotations at all, the description omits any mention of scope limits (e.g., shared vs personal lists) or safe read behavior, leaving minor gaps.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The description correctly signals that no filtering arguments exist by saying 'todas'.

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 ('Devuelve todas las listas de compra del hogar') and names the returned fields (IDs and names), so the agent knows exactly what it gets. It does not distinguish itself from siblings like get_or_create_shopping_list or get_shopping_list_items, so an agent must infer the difference.

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?

Usage is only implied: 'todas las listas del hogar' suggests a discovery/listing call, typically used before add_to_shopping_list or get_shopping_list_items. There is no explicit when-to-use, when-not-to-use, or named alternative, so routing between the many shopping-list siblings is left to inference.

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