Check Balance

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

Annotation s already indicate read-only, non-destructive, and idempotent behavior. The description adds that the tool returns balance in SOL, ready-to-stake status, and next steps, providing behavioral context beyond annotations.

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, front-loaded sentence that conveys key information without any unnecessary content.

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 the simple input and rich annotations, the description covers the core purpose and return fields. It lacks details on the structure of 'ready-to-stake status' and 'next steps', but remains fairly complete for a balance-check tool.

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?

Schema coverage is 100% with the parameter 'walletAddress' already well-described. The description does not add new parameter semantics beyond what the schema provides.

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 the tool checks SOL balance of any Solana wallet address, specifying the resource and action. It distinguishes from siblings like check_address_type by focusing on balance.

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?

The description implies usage for checking balance but does not provide explicit guidance on when to use this tool vs alternatives (e.g., check_stake_accounts). No when-not-to or alternative mentions.

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