wise_list_recipients

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no additional behavioral context such as authentication requirements, rate limits, or what happens with invalid profile IDs. The bar is lower due to annotations, but the description adds minimal value beyond them.

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 two sentences with no wasted words. The first sentence states the primary action, and the second provides a specific usage hint. It is front-loaded and efficient.

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 is simple (list with optional filter) and has full schema coverage, but no output schema. The description does not mention what is returned (e.g., an array of recipient objects with fields like id, currency, name). For completeness, it would benefit from clarifying the return format, though the annotations and sibling tools provide some implicit context.

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%, so baseline is 3. The description adds an example ('e.g. EUR beneficiaries') for the currency parameter, but the schema already describes it as an optional ISO-4217 filter. The description does not significantly enhance understanding beyond the schema's own descriptions.

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 'List recipient accounts for a profile,' using a specific verb and resource. It distinguishes from sibling tools like 'wise_get_recipient' by implying multiple accounts, and the sibling list tools are similarly 'list' operations. The filtering example adds precision.

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 offers guidance on filtering by currency, e.g., 'if you only want e.g. EUR beneficiaries,' which helps the agent decide when to use the currency parameter. However, it does not explicitly state when to use this tool over alternatives like 'wise_get_recipient' or provide exclusions.

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