チェーンの現況

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

注解已声明 readOnlyHint=true、destructiveHint=false、openWorldHint=true，安全属性覆盖充分。描述未披露额外行为（如缓存、速率限制），但也没有矛盾。由于注解已负担安全上下文，描述未添加更多行为信息，因此评为中等。

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?

描述为一句紧凑的日文句子，信息完整，无冗余。开头即点出返回内容，后接使用场景，效率极高。

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?

工具参数少且简单，注解已涵盖安全性，描述充分覆盖目的和返回值，虽无输出 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?

参数 network 的 schema 覆盖率为100%，描述仅复述了 schema 中的默认值和可选值，没有新增语义。按规则高覆盖率时基线为3，无额外补偿。

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?

描述明确“返回链 ID、最新区块、基本费用和拥堵程度”，并指明这是“查看网络当前状态的初始工具”。动词“返回”与资源“链信息”明确，与兄弟工具（如 read_block、account_info）区分清晰。

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?

描述提到“第一次查看网络状态”，暗示了适用场景，但没有明确说明何时不使用，也未指出替代工具。缺乏明确的“当……时使用”或“而非……”的排除条件，指南尚可但不够完整。

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