get_sol_balance

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

The description discloses the return format (dict with lamports and sol) and indicates the address parameter, but does not mention side effects, authentication requirements, rate limits, or error handling. Since no annotations exist, the description carries full burden, but it lacks depth beyond return structure.

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 concise with no redundant words. It clearly separates the purpose, input arguments, and return value into distinct sections. 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?

The description covers the essential information: what the tool does, the required parameter format, and the return value structure. However, it omits edge cases (e.g., invalid address handling) and does not clarify whether the tool is a read-only operation. Given the tool's simplicity, it is mostly complete.

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 parameter 'address' has schema coverage 0%, but the description adds critical context: it must be a Base58-encoded account/wallet address. This goes beyond the schema's type definition and helps the agent construct valid input.

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 retrieves the native SOL balance of a Solana account, using a specific verb and resource. It uniquely distinguishes itself from sibling tools like get_account_info or get_token_holdings.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The agent is left to infer usage from the tool's name and brief description alone.

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