list_volumes

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

With no annotations, the description carries the full burden. It clarifies that the tool is a read-only listing operation and the kind of data returned, but it does not mention potential size limits, ordering, empty-case behavior, or whether it simply summarizes all volumes. Basic transparency is present, but behavioral depth is limited.

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?

The core description is concise and front-loaded. However, the third sentence about arg structure adds no value, obscures the real required parameter, and could mislead an agent. Overall length is appropriate but the structure is weakened by that misleading parameter note.

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?

The description explains the purpose well but is incomplete for invocation: it omits the required case_id parameter entirely. While an output schema exists and the tool is conceptually simple, lacking mention of the one required input means the agent cannot reliably call it.

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?

The schema requires a case_id, but the description does not mention it at all. The only parameter-related text says '参数结构（args 字段）: {}', which is misleading because args is optional and can be any object or null, while case_id is the actual required input. With 0% schema description coverage, this is a critical gap.

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 states a specific action and resource: listing all volumes in the case, with the exact fields returned (volume name, file name, total pages). It does not explicitly differentiate from siblings like get_volume_outline, but the scope '全部卷宗' and the listed output fields make the purpose clear.

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?

The description explicitly says this should be called first when reviewing a case, which is clear usage guidance. However, it does not mention when not to use it or how to choose between it and related tools like search_volumes or get_volume_outline.

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