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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds the ownership scope (wallet owned by the authenticated participant) but does not disclose return shape or failure behavior; this is acceptable given the annotations but adds only modest context.

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 focused sentence delivers the core purpose and ownership constraint without any wasted words. It is front-loaded and easy to scan.

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 one-parameter read operation with readOnly and destructive annotations, the description is nearly complete. It could mention the return value explicitly, but 'Read one wallet' strongly implies the wallet object is returned, so the gap is minor.

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 0%, so the description carries the burden for explaining the parameter. 'Read one wallet' combined with the parameter name 'walletId' reasonably implies that walletId identifies which wallet to read, though the description never explicitly says so or notes expected format or ownership constraints.

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 ('Read') and a precise resource ('one wallet owned by the authenticated participant'), which clearly identifies the operation and object. This distinguishes it from siblings like create_wallet (write) and get_balance (different resource).

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 when to use the tool—when you need a single wallet for the authenticated participant—but it does not state when to avoid it or name alternative getters. There are no exclusions or explicit sibling comparisons.

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