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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description still adds real value beyond that: 'never sends funds' and 'unsigned transfer instructions' clarify that even the amount path produces non-executing output, and 'owner-activated' hints the address may not exist until the owner enables it. It stops short of describing failure modes or output format.

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?

Two tight sentences with the core purpose front-loaded and the no-funds guarantee immediately after. Every clause contributes new information, with no filler or repetition of the title.

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 one-parameter read tool with no output schema and readOnlyHint=true, the description covers what is returned (address, or unsigned transfer instructions) and the critical safety boundary. Only minor gaps remain around when the address is unavailable and how the amount is denominated.

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 description coverage is 0%, so the description carries the burden for the single optional 'amount' parameter. It explains the functional effect (returns unsigned transfer instructions instead of just the address), which is the most important semantic, but it omits units/denomination, rounding, and the meaning of the pattern constraints already encoded in 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 names a specific verb and resource ('Read the owner-activated USDC receiving address on Base') plus the network, so the operation is unambiguous at a glance. Adding that an optional amount yields 'unsigned transfer instructions' and that it 'never sends funds' further pins down exactly what the tool does versus a generic payment tool.

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?

It implies two usage modes: call with no argument to get the address, or with an amount to get transfer instructions. However there is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives among siblings like submit_offer. Usage is inferable rather than stated.

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