wallet_info

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

With no annotations, the description carries the full burden of disclosing behavior. It only states the cost ($0.001 USDC via x402) and the vague category 'x402 & Wallet tool'. It does not disclose whether the operation is read-only, what it returns, or any side effects, leaving the agent blind to critical behavioral traits.

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 extremely brief, consisting of a fragment and a cost note. While it is concise, it is under-specified; it does not convey the tool's purpose or behavior. The brevity is not used effectively to front-load key information.

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?

The tool lacks an output schema and annotations, so the description must be self-sufficient. It fails to explain what 'wallet info' entails, what x402 is, how the tool works, or what the response will provide. The presence of a sibling 'x402_wallet_info' further highlights the need for clearer scoping, which is absent.

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 one generic 'params' object with a description that covers 100% of the schema properties, so the baseline is 3. However, the description adds nothing about the actual parameters and the nested object remains a black box, so it does not compensate for the lack of meaningful parameter details.

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 essentially a restatement of the name ('wallet info') with vague context ('x402 & Wallet tool'). It lacks a clear verb or action, leaving the user to infer that it retrieves wallet information. It also does not distinguish itself from the sibling tool 'x402_wallet_info'.

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 any alternative. The description mentions cost but does not explain the appropriate context for invocation or any exclusions. With a nearly identical sibling (x402_wallet_info), the lack of differentiation is a significant gap.

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