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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It explicitly states that the tool returns information and specifies a default (USDC on Base), which is transparent for a simple read-only getter. It does not mention potential errors or side effects, but for a parameterless query, this is adequate.

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, well-structured sentence that front-loads the primary action and result. It includes a valuable default clarification without any wasted words. Concise 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?

For a parameterless getter with a clear return specification, the description is complete. It tells the agent exactly what to expect (pay-to address and stablecoin rail) and the default. No output schema exists, but the description sufficiently explains the result. There are no missing elements for correct invocation.

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 tool has zero parameters, so the schema provides full coverage. The baseline for 0 parameters is 4, and the description adds no parameter-specific information (nor is any needed). This score reflects that the schema is complete and the description does not need to compensate.

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 states a specific verb ('Return') and the exact resources: pay-to address and preferred stablecoin rail. It also clarifies the default rail, making it distinct from sibling tools that handle orders, agents, or listings. This is a clear, unambiguous purpose.

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?

No guidance is given on when to use this tool versus alternatives. The description does not mention conditions, prerequisites, or any contrasting tool that might be more appropriate in certain scenarios. This is a significant omission given the existence of siblings like fulfill_order and list_service.

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