list_lvm_volumes

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

No annotations are provided, so the description must disclose behavioral traits like idempotency, permission requirements, or side effects. The description only says 'List...', implying read-only but not explicitly stating it. No mention of auth needs, error behavior, or impact on state.

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 extremely concise at two sentences, with no redundant information. However, the structure could be improved by using a more organized format (e.g., separating the main action from parameter details), but it remains efficient and front-loaded.

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 an output schema (assumed present but not shown), yet the description does not explain return values or pagination. Given the simple nature of listing volume groups, the description should state what fields are returned or that the list may be empty. Lack of completeness for a list 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?

The parameter 'node' has 0% schema description coverage, meaning the schema provides no details. The description adds only 'The node name', which is virtually identical to the parameter name. No additional context like allowed format, required permissions, or relation to other components is provided.

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?

Description states verb 'List' and resource 'LVM volume groups' on a node, clearly differentiating from sibling list tools like 'list_lvmthin_pools' or 'list_storage'. However, the tool name says 'volumes' while description says 'volume groups', creating a potential conceptual mismatch that slightly reduces clarity.

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 on when to use this tool versus alternatives (e.g., list_lvmthin_pools, list_storage_content). No prerequisites, conditions, or scenarios mentioned, leaving the agent without context to select the appropriate tool among many similar list tools.

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