Listas guardadas del usuario

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

No annotations are provided, so the description carries full burden. It discloses the need for a logged-in session, direct JSON call, prohibition of DOM scraping, and that the server never handles credentials. This provides substantial behavioral context despite limited annotation support.

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 adequately structured with purpose first, then instructions. However, it is somewhat verbose, mixing instructions with warnings. It could be more concise while retaining key information.

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 explains the user workflow, expected input format, and normalization of output. It also warns against scraping. Given the tool's complexity (external session), it covers most contextual needs, though error handling and edge cases are absent.

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 coverage is 100% with descriptions for store, branchId, and rawLists. The description adds operational context (e.g., rawLists comes from a browserSnippet) but does not significantly deepen parameter meaning beyond what the schema already provides.

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 it returns saved shopping lists normalized to { id, name, items[] }. It provides a specific verb and resource. However, it does not explicitly distinguish this tool from siblings like get_frequent_purchases, which could be a similar retrieval tool.

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 explains the required session and browser workflow, implying when to use it (when lists are needed). However, it lacks explicit when-not-to-use or comparison to alternative tools, leaving some ambiguity about exclusivity.

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