Get Wallet Address

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

No annotations are provided, so the description carries full burden. It mentions 'sanitized wallet details' but offers no additional behavioral context such as read-only nature, authentication needs, rate limits, or what 'sanitized' entails.

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?

A single concise sentence (12 words) that is front-loaded with the action verb. No redundant phrasing or unnecessary details.

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 simple single-parameter tool, the description covers the core purpose. However, with no output schema and minimal descriptions, it leaves the return value vague ('sanitized wallet details') and fails to specify whether it returns a single object or other structure.

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 defines a single required string parameter with URI format. The description adds domain context by referring to it as an 'Open Payments wallet address', but it does not elaborate on input expectations or edge cases beyond the schema.

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 uses a specific verb 'Resolve' with a specific resource 'Open Payments wallet address', clearly distinguishing it from sibling tools focused on grants, quotes, and payments.

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 a lookup/resolution use case, but does not explicitly state when to use it versus alternatives (e.g., before creating payments). No exclusions or alternative tool references are provided.

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