list_storage_disks

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'list', implying a read operation, but fails to mention authentication needs, parameter-driven filtering, or return structure. The folder_id param suggests filtering, but the description claims 'all' without addressing this.

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 single sentence is concise and front-loaded, but it omits necessary context about the parameter and return behavior. It is under-sized rather than appropriately sized for a tool with a parameter.

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?

For a tool with one optional parameter and no output schema, the description is severely incomplete. It doesn't explain folder_id, the effect of null, or the structure of the returned list, leaving major gaps in the agent's understanding.

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 0% description coverage for folder_id, and the description does not mention the parameter at all. The agent cannot infer what folder_id does, whether it filters, or how it affects the result.

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 uses a specific verb ('List') and resource ('storage disks'), clearly indicating it returns all disks. It doesn't explicitly distinguish from siblings like get_disk_details, but 'all' implies a listing operation rather than a detail fetch.

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 others. There is no mention of alternatives, prerequisites, or contextual triggers, leaving the agent without direction on selecting this over sibling tools.

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