get_account_info

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

With no annotations, the description must carry the safety profile; 'Get' implies a read operation, and it discloses that nonce and balance are returned. It does not state whether it queries the network, what happens when the address is omitted (that is left to the schema), or what errors/permissions may apply, so the disclosure is partial.

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 first sentence is front-loaded and efficient, but the second sentence is a promotional cross-sell unrelated to selecting or invoking this tool. Roughly half the description is therefore not earning its place.

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?

This is a simple read tool with one optional parameter and no output schema, so the burden is modest. However, 'detailed account information' is vague beyond nonce and balance, and with no output schema the agent has no way to know what else is returned or how the data is scoped.

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% and the single optional 'address' parameter is already documented as defaulting to the configured wallet. The description adds no extra meaning about the address parameter (e.g. network or validation requirements), so baseline 3 applies.

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 names a concrete verb and resource ('Get detailed account information') and discloses two specific returned fields (nonce, balance), which is more than a tautology. It does not distinguish itself from close siblings such as get_wallet_info, get_stx_balance, or get_btc_balance, leaving the agent to guess which account view to call.

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?

There is no statement of when to use this tool versus get_wallet_info or get_stx_balance, and no prerequisites or exclusions. The only routing hint is a promotional tip pointing at earning_opportunities, which is unrelated to deciding when this tool is the right choice.

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