list_wishlists

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

No annotations are provided, so the description carries the full behavioral burden. It communicates a read-only listing operation and promises IDs/contents, but it does not disclose login requirements, empty-result behavior, or what 'shared' means for visibility and access. This is not ideal but is adequate for a simple list operation.

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 first sentence is concise and informative. The second sentence, 'This shows the shared shopping lists,' is largely redundant with the first and introduces ambiguity about whether the lists are personal or shared, so not every sentence earns its place.

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?

For a parameterless listing tool with no output schema, the description is nearly complete: it names the resources, the scope ('all'), and the important returned fields (IDs and contents). The main soft spot is the unresolved 'shared shopping lists' phrasing and the lack of an explicit authentication note, but overall the description is sufficient for correct invocation.

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 has zero parameters and schema coverage is 100%, so there is no parameter burden on the description. With 0 parameters, the baseline is 4; no parameter information is missing or unclear.

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 ('List'), resource ('all your Webhallen wishlists'), and the returned data ('IDs and contents'). The qualifier 'all' clearly distinguishes it from get_wishlist, which presumably targets a single wishlist.

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 intended usage is implied: use this tool when you need the full set of wishlists rather than one specific list. However, it does not explicitly name get_wishlist as the single-list alternative or state when not to use this tool.

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