get_storage_disk

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

No annotations are provided, so the description carries the full burden. It lists several error codes (e.g., 'not_found', 'invalid_disk'), which gives insight into possible failure modes. However, it does not mention authentication, rate limits, or whether the operation is read-only, which are typical behavioral expectations for a 'get' tool.

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 concise, with the purpose front-loaded in a single sentence. The error codes are appended. It is appropriately sized and avoids redundancy, though the error codes could be better structured (e.g., grouped by type).

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 no parameters and an output schema, the description does not need to explain return values. It provides the core purpose and error codes. However, it lacks usage context (e.g., when to use vs. other storage tools) and does not address potential behaviors like pagination or the effect of missing disks.

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 tool has zero parameters, and the schema description coverage is 100% (trivially). With no parameters, the description does not need to add parameter semantics. The baseline for 0 parameters is 4.

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 'Returns the collection of all StorageDisk', which clearly indicates the verb and resource. It distinguishes from siblings like get_storage_disk_id by implying it retrieves all disks, but does not explicitly differentiate from other storage-related 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?

The description provides no guidance on when to use this tool versus alternatives such as get_storage_disk_id or get_storage_partition. It does not specify any conditions or context for use.

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