List node disks (basic)

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that it returns 'basic disk inventory,' which implies a non-destructive read operation. However, it does not elaborate on what 'basic' entails or any potential constraints.

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 6 words. While efficient, it sacrifices completeness. It is well-structured but could benefit from slightly more detail 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 tool has one parameter, no output schema, and a sibling tool for detailed disks, the description is incomplete. It does not specify what fields are included in 'basic disk inventory,' leaving the agent unaware of the output structure.

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 description does not explain the 'node' parameter beyond noting the operation is 'on a node.' With 0% schema description coverage, the description fails to provide necessary details about parameter format (e.g., hostname, IP) or constraints.

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 clearly states the tool returns 'basic disk inventory on a node,' using a specific verb and resource. It distinguishes itself from the sibling 'list_node_disks_detailed' by emphasizing 'basic' inventory.

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 provided on when to use this tool versus 'list_node_disks_detailed' or other similar tools. The description lacks context for choosing this tool over alternatives.

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