List VolumeSnapshot CRs

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

No annotations are present, so the description carries the full burden. It only says 'List', which implies a read operation, but does not disclose behavior such as whether it returns a flat list or detailed objects, any pagination/limits, or authentication requirements. The doc link adds external reference but not internal behavioral transparency.

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 one sentence that immediately states the action and resource, followed by a relevant doc link. No filler or redundant phrasing. The purpose is front-loaded, and the link provides optional depth without cluttering the core definition.

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 tool has one required parameter, no output schema, and no annotations, so the description carries most of the context. It correctly identifies the resource and volume association, and the doc link offers deeper setup context. However, it lacks any indication of return format, available fields, or edge cases, leaving some ambiguity for a minimally described read operation.

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 coverage is 0% for the single required 'name' parameter, but the description says 'for a volume', which strongly implies the parameter is the volume name. This adds meaning beyond the schema, though it does not clarify expected format, exact resource type, or whether other optional parameters exist.

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 resource ('CRD-backed snapshots for a volume'), which distinguishes it from regular volume snapshot tools like volume_snapshot_list. The CRD qualifier and volume context clarify what this tool operates on, though it stops short of explicitly comparing with sibling tools.

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?

No guidance is given on when to use this tool versus alternatives such as volume_snapshot_list, snapshot_list, or volume_snapshot_cr_get. The 'CRD-backed' qualifier implies a usage context, but without exclusions or alternative routing, the agent is left to infer the appropriate scenario.

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