get_wallet_address

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

With no annotations, the description carries full burden. It discloses that the tool starts a WebSocket connection as a side effect, which goes beyond mere derivation. It does not mention prerequisites like the private key being set, but the description is transparent about the key action.

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 sentences with no wasted words. The main action is front-loaded, and the side effect is stated concisely. Every sentence adds value.

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?

Given no parameters and no output schema, the description explains the main function and side effect. It does not describe the return format of the wallet address, which is a minor gap, but overall the tool is simple enough that this is acceptable.

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 input schema has no parameters, so schema description coverage is 100%. The description adds meaning by specifying the source (TRADEROUTER_PRIVATE_KEY), which is not in the schema. This compensates fully for the absence of parameters.

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 clearly states it derives a Solana wallet address from TRADEROUTER_PRIVATE_KEY. The verb 'derive' is specific, and the resource is the wallet address. This tool is distinct from siblings like auto_swap or place_order, which handle trading operations.

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?

Explicitly indicates 'Call first at session start' and mentions starting a WebSocket connection, providing clear temporal and contextual guidance. No alternative tools are listed, but the unique initialization role makes this sufficient.

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