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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. The description adds crucial context: session requirements, auth mode resolution, and constraints (TRX only, min 10 TRX, read-only). No contradictions.

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?

Description is front-loaded with purpose, then session requirements, then constraints. Slightly verbose with full auth mode explanation, but all information is relevant and well-structured.

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 simple single-parameter tool with output schema (implied), the description covers purpose, preconditions, constraints, and safety profile completely. No missing critical context given existing annotations and schema.

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% and the parameter (amountTrx) is well-documented with type, minimum, and description. The tool description repeats the min deposit (10 TRX) but adds no new semantic nuance beyond what the schema provides.

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 'Fetches the specific deposit address for the TronSave internal account,' with a specific verb and resource. It distinguishes itself from sibling tools (none others fetch deposit addresses) and adds constraints (TRX only, min 10 TRX).

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?

Explicitly states the prerequisite of a logged-in session via tronsave_login, provides the required session header format, and explains when to trigger ('if the user asks for a deposit address or needs to top up'). Also clarifies auth modes.

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