move_list_volumes

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

Annotations already declare readOnlyHint and openWorldHint, so the description's main job is to add domain context beyond those signals. It adds the scoping qualifier 'calibration volumes', but it does not disclose pagination behavior, expansion options, or other operational traits beyond what the annotations already imply.

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 description is very concise and front-loaded, with no wasted words. However, it provides only the minimum viable information and lacks useful operational context expected from a paginated list tool.

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?

Even though an output schema and annotations are present, the description omits the relationship to sibling volume tools, the intended meaning of 'calibration volumes', and any guidance on pagination or expansion. For a tool with four optional parameters, this is incomplete.

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 only 25%, with 'after' being the only parameter described in the schema. The description provides no parameter-level meaning and does not compensate for the low coverage of first, expand, or sort_direction.

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 verb ('List') and a specific resource ('calibration volumes'), so an agent can tell that this is a read-only listing operation. It does not explicitly distinguish itself from move_get_volume or move_create_volume_with_human, so it stops short of a 5.

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?

There is no guidance about when to use this tool versus alternatives such as move_get_volume or move_create_volume_with_human. The intended usage must be inferred entirely from the tool name and the sparse description.

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