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

With no annotations, the description carries the full transparency burden. It usefully discloses the returned status fields, but says nothing about rate limits, network/permission requirements, or error behavior when a chain is unsupported.

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?

Compact and front-loaded: purpose plus returned fields first, then the when-to-use routing note. Every sentence carries signal with no padding.

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 one-parameter read tool with 100% schema coverage and no output schema, the description supplies returns, usage trigger, and the alternative tool, which is sufficient to call correctly. The only residual gap is the missing rationale versus chain_status.

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 a single enum-constrained 'chain' parameter, so the schema already fully documents the input. The description adds only the human-language restatement (doge/ltc) and no extra syntax or default details, so the baseline of 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?

States a specific verb and resource (查询 DOGE/LTC 节点状态) and enumerates exactly what is returned (高度、同步进度、连接数、内存池笔数), which lets an agent distinguish it from the sibling chain-specific tools. It also explicitly delimits scope to DOGE/LTC, ruling out the other chains.

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 an explicit trigger ([何时用] 问狗狗币/莱特币节点进度) and routes non-DOGE/LTC chains to chain_status. It does not explain why one would pick this over chain_status for a doge/ltc query, even though chain_status reportedly accepts any chain, leaving a slight routing ambiguity.

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