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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint false, so the safety profile is covered. The description adds genuinely useful context beyond that: the api_key auth requirement, the register_agent prerequisite, the recommended funding rail, and how to confirm credit afterward.

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?

It is a single dense sentence sized appropriately for a one-parameter tool, with no wasted filler. However, it opens with the parameter prerequisite rather than the operation, so the core purpose is not perfectly 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?

For a single-parameter read with no output schema, the definition covers prerequisites, recommended rail, and post-call verification adequately. The per-chain structure of the returned addresses is only implied, which is a minor gap.

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 description coverage is 100%, so the schema already documents the single api_key parameter. The description's note that the key comes from register_agent largely repeats the schema's own parameter description rather than adding new syntax or format detail. Baseline 3 is appropriate.

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?

States a specific verb (Get) and resource (deposit addresses) with a clear scope qualifier: 'YOUR agent account's own per-chain deposit addresses to fund it'. There is no overlapping sibling, and the purpose is unmistakable without opening the schema.

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?

Gives clear usage context (fund your own account), a recommended rail (USDT on Ethereum mainnet), a prerequisite (register_agent), and a companion verification step (GET /api/v1/account/me/balances). It stops short of explicit when-not guidance, so it is not a full 5.

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