wishlist_list

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

No annotations exist, so the description must stand alone. 'List' implies a non-mutating read, but the description does not disclose output format, pagination, or any edge cases beyond the bare action.

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 four words and immediately states the action and subject. There is no filler or redundancy, making it an efficient definition for a simple list tool.

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 tool has an output schema and no parameters, so minimal description is required. It is mostly complete for a simple list operation, but could benefit from noting its relationship to 'searches' or 'wishlist_check' to prevent ambiguity.

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?

There are zero parameters, so the empty schema is fully covered and there is nothing additional for the description to explain. Baseline of 4 applies.

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?

Description uses specific verb 'List' and resource 'standing wishlist searches', clearly identifying it as a read-only operation. It differentiates from mutating siblings like wishlist_add and wishlist_remove, though it does not explicitly distinguish from similar 'searches' sibling.

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 given on when to use this tool versus the sibling tools. It does not mention alternatives, prerequisites, or scenarios, leaving the agent to infer usage from the name alone.

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