list_storage_paths

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds light behavioral context by mentioning pagination and the domain purpose of storage paths, but it does not disclose return shape, defaults, or any additional behavior. No contradiction with annotations exists.

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?

Two short sentences, action first, no wasted words. The second sentence adds useful domain context that is not present in the schema or annotations.

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?

Adequate for a simple, read-only list tool, but there are clear gaps: no output schema exists and the description does not describe the response shape, filter parameter behavior, or default pagination behavior. It is minimally viable but not richly complete.

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?

Schema description coverage is only 29%, so the description carries substantial responsibility for explaining parameters. It only says 'optional filtering and pagination' without naming the filter fields, their meanings, or ordering semantics. The name__* parameters and ordering remain effectively undocumented.

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 a clear verb ('List'), a specific resource ('storage paths'), and scope ('all'), with optional filtering and pagination. It is readily distinguishable from get_storage_path by the plural 'all', though it does not explicitly name a sibling or contrast itself with the single-item lookup.

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 use case is implied: call this to list storage paths rather than to fetch one specific path, which would be get_storage_path. There is no explicit when-to-use/when-not-to-use guidance or mention of alternatives.

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