x402_wallet_info

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

The description discloses a cost ('$0.001 USDC via x402'), which is a behavioral trait, but nothing else. With no annotations, the description fails to convey what happens during execution, potential side effects, or return formats.

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 very short but the single sentence is largely tautological ('x402 wallet info — x402 & Wallet tool') plus a cost note. It is under-specified rather than concisely informative, so the sentence does not earn its place.

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?

With no annotations and no output schema, the description must carry full context. It provides no details on what wallet information is returned, required inputs, or expected behavior, leaving the tool essentially undocumented.

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 has a single generic 'params' property described as 'Tool parameters as JSON object,' giving 100% schema coverage. The baseline of 3 applies because no parameter info is added in the description, but the generic wrapper makes this minimally acceptable.

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 is tautological: 'x402 wallet info' restates the tool name and 'x402 & Wallet tool' is a label rather than a statement of function. It provides no specific verb or resource describing what the tool actually does.

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 provided on when to use this tool versus alternative wallet-related tools like wallet_info or payment tools like x402_payment_request. There are no prerequisites, exclusions, or context signals.

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