网关接口清单

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

注解已声明 readOnlyHint=true、openWorldHint=true、destructiveHint=false，描述没有与之矛盾。描述补充了“当前可用”这一动态性信息，并说明该工具是用于检查能力存在性和参数变化，但未进一步说明返回内容的结构特点或可能的体积问题。在注解已覆盖安全画像的情况下，这是可接受的中间水平。

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?

描述仅两句话，第一句直接说明工具行为和资源，第二句给出使用场景与排除场景，信息密度高、无冗余。内嵌的 JSON 示例虽简短但具有实际参考价值，整体结构清晰且关键信息前置。

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?

该工具参数数量为 0，schema 覆盖率为 100%，参数语义主要由 schema 承担。描述中给出的 `{"api_name": "/_list"}` 作为调用示例增加了上下文，说明该工具本身如何触发清单返回，虽未涉及参数说明，但对零参数工具来说已足够。

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?

描述以明确动词“列出”指出资源是“微信读书网关当前可用的全部接口及参数定义”，并给出调用示例 `{"api_name": "/_list"}`，让代理能准确理解工具作用。与 call_gateway 等兄弟工具相比，它明显是“接口清单”而非具体业务查询，具有区分度。

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?

描述明确给出使用场景“用于排查某个能力是否还存在 / 参数是否变化”，并明确说明“日常问答不需要调用”，具备明确的 when 与 when-not 指引。但没有直接点名替代工具（如 call_gateway 或具体查询类工具），因此未达到最高分。

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