get_wallet_info

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

No annotations are provided, so the description carries the burden. 'Get' implies a read-only operation and it usefully discloses the no-wallet fallback behavior (returns guidance rather than failing), but says nothing about auth requirements, whether it triggers wallet creation, or what 'status' comprises.

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 short sentences with the core action front-loaded, followed by the fallback behavior. The trailing 'Tip: call earning_opportunities' is marginally promotional but still earns its place as agent routing.

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 zero-param read tool with no output schema and no annotations, the description is close to complete: it names the returned concepts (address, status) and the edge case. It would be stronger if it briefly characterized what 'status' contains, since there is no output schema to fall back on.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. The description correctly presents this as a no-argument self-query.

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?

States a specific verb and resource: retrieve the agent's own wallet address and status, plus a fallback behavior when no wallet exists. It does not differentiate from closely related siblings like wallet_status, wallet_list, or pillar_key_info, which an agent could easily confuse with this.

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?

Usage is implied (call this to learn your wallet address/status, and it self-routes to guidance when no wallet is assigned), and there is a cross-sell tip to earning_opportunities. No explicit when-to-use-this-vs-wallet_status guidance or prerequisites are given.

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