account_info

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

No annotations are provided, so the description carries the burden of disclosure. It usefully reveals the types of data returned (free extractions, balance, wallets) and the verb 'Get' implies a read-only operation. However, it does not discuss potential errors, authentication requirements beyond the API key, or any side effects.

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?

A single, focused sentence that is front-loaded with the primary purpose and includes specific details. It is efficiently concise with no wasted words.

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 sufficient for a simple, one-parameter read-only tool. It lists the key return contents, making the tool self-explanatory. The absence of an output schema is adequately compensated by listing what the caller can expect. A small deduction because it could mention that it is a safe/read operation more explicitly.

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 fully covers the single parameter (api_key) with a clear description and prefix hint. The tool description does not add additional parameter meaning, so the baseline of 3 is appropriate since the schema already documents the parameter.

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 uses the specific verb 'Get' and clearly identifies the resource (account info) along with concrete contents (free extractions, USDC balance, associated wallets). It is distinct from sibling tools like register, extract_url, add_wallet, and deposit.

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 when account details are needed, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. For example, it does not say 'use this to check your balance before extracting' or compare with other tools.

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