wise_get_transfer

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

Annotations declare readOnlyHint=true and openWorldHint=true, which the description complements by specifying the returned data categories. However, it does not disclose any additional behavioral traits such as required permissions or rate limits, so it adds some but not substantial transparency.

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 a single sentence that is front-loaded with the main action and includes supplementary details in parentheses. It is concise with no redundant 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?

Despite the absence of an output schema, the description lists the main categories of returned data (status, amounts, recipient, quote, timestamps), which provides a good overview for a simple get resource. It does not cover error cases or edge scenarios, but is sufficient for a basic read operation.

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 schema already provides a description for transferId (from list_transfers), and the tool description merely repeats that it gets 'by ID' without adding new meaning. With 100% schema coverage, the description does not enhance parameter understanding significantly.

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 the tool retrieves a specific transfer by ID, listing key data fields (status, amounts, recipient, quote, timestamps). This differentiates it from sibling tools like wise_get_profile or wise_get_recipient, so the purpose is specific and unambiguous.

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 implies usage when you have a transfer ID (from list_transfers), but does not explicitly state when to use this tool versus alternatives like wise_list_transfers for multiple transfers, or other get tools. No exclusion criteria are provided.

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