get_account_info

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

With no annotations, the description carries the full burden of disclosure. It implies read-only behavior by stating it 'gets' information, but does not explicitly confirm no side effects, auth requirements, or error handling (e.g., behavior for invalid addresses). The list of returned fields adds some transparency.

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, well-structured sentence that conveys the core functionality without redundancy. It could be slightly expanded for clarity on return values, but overall it is efficient and front-loaded.

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 is adequate for a simple read tool with two parameters and no output schema, listing key return fields. However, it doesn't guarantee exhaustiveness or mention missing fields, and lacks any example or edge-case behavior.

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 descriptions for both parameters. The description adds context about what the tool returns, but does not clarify parameter-specific details like format or validation. Baseline 3 is appropriate given high schema coverage.

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 detailed account information for a Solana address, specifying fields like owner, lamports, data size, and executable status. It distinguishes itself from sibling tools like 'get_balance' or 'get_token_accounts' by focusing on general account details.

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 instead of alternatives. For example, it doesn't differentiate from 'get_balance' (which only returns lamports) or 'read_account_data'. An AI agent would have to infer usage context without explicit direction.

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