list_directory_storage

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states the action ('List') without revealing whether the operation is read-only, requires authentication, or has side effects. For a list operation, safety may be implied, but the description fails to explicitly convey behavioral traits.

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 (two sentences) and front-loads the purpose. While it is appropriately sized, it could be enhanced with minor details without becoming verbose. The structure is functional but minimal.

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 (not shown) which may convey return values, so the description need not explain them. However, it lacks context about what 'directory-based storage mounts' are, how the node is specified, or any prerequisites. Given the simple input, it is minimally complete but could be more helpful.

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 input schema parameter 'node' has 0% description coverage. The description adds only 'The node name', which is redundant with the schema's title. No values, format, or constraints are explained. Since schema coverage is low, the description should compensate but barely does.

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 that the tool lists directory-based storage mounts on a node, using a specific verb and resource. It distinguishes itself from siblings like list_storage (which lists all storage) and list_node_storage by specifying 'directory-based', making its purpose precise.

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 vs alternatives. There is no mention of when not to use it, nor any reference to sibling tools like list_storage which may be more appropriate for general storage listing. The agent is left to infer usage context.

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