List storage paths

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds useful context: storage paths are filename templates controlling on-disk location, the default return shape is a summary, and reuse is the recommended behavior.

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?

Three short sentences carry the action, the domain definition, and the usage recommendation. The opening 'List storage paths' is slightly redundant with the title, but there is no filler or bloat.

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 simple list operation with rich annotations and a fully described schema, the description supplies the missing context: what a storage path is, what the default response contains, and when to call this tool. It would be slightly stronger if it named the specific sibling for creating a path, but the guidance implies it clearly.

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 100% and every parameter has its own description, so the baseline is 3. The tool description adds no parameter-level meaning beyond what the schema already provides.

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?

States a specific verb and resource ('List storage paths'), defines what a storage path is, and names the default return fields (id, name, document_count). This clearly distinguishes it from siblings such as get_storage_path or create_storage_path by its collection-level read action.

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?

Explicitly instructs 'Call this before creating anything' and notes that reusing an existing path is 'almost always correct', which implies the alternative (creating a new storage path) should be avoided unless necessary. It does not enumerate sibling tools or other exclusions, so it stops short of full when-not-to-use guidance.

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