list_disk_snapshots

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

With no annotations, the description carries the full burden, but it only states a basic list operation. It does not disclose whether the tool is scoped to a folder, whether it returns only snapshots owned by the current user, or any authentication/authorization requirements. The 'all' phrasing is also potentially misleading given the folder_id parameter.

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 a single, front-loaded sentence with no wasted words. It is appropriately concise for a simple list operation, though it could be augmented without becoming verbose.

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?

Given the lack of annotations, output schema, and any parameter explanation, the description is under-specified. It does not clarify the role of folder_id, the output format, or edge cases like empty results or permission errors. This makes the tool only minimally comprehensible.

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 has one optional parameter (folder_id) with zero description coverage, and the description does not mention it at all. This leaves the parameter's meaning entirely unexplained, though the default of null and the parameter name provide some hint. A brief note that folder_id filters the listing would have helped.

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 'List all disk snapshots' uses a specific verb ('list') and a clear resource ('disk snapshots'), and the name itself distinguishes it from siblings like get_snapshot_details (which targets a single snapshot) and list_storage_disks (which targets disks). However, it does not explicitly state that it can be filtered by folder_id, which would make the 'all' claim ambiguous.

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 on when to use this tool versus alternatives such as get_snapshot_details or how the optional folder_id parameter influences the result set. No context is given about prerequisites, scoping, or when a user might prefer a different tool.

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