List Files in Connected Storage

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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description adds value beyond them: it states auth requirements (configured API key with storage access), confirms the bucket is never changed, and reveals behavioral details like returned cursors and ready-made URIs. No contradiction with annotations.

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 tight sentences with no filler. The primary purpose is front-loaded, followed by the most useful operational details (URIs, prefix navigation, cursor pagination, auth, read-only guarantee) in order of importance.

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 read-only listing tool with a full output schema and complete parameter docs, the description covers invocation details, pagination behavior, auth prerequisites, and safety. Nothing essential is missing for an agent to call it correctly.

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 covers all four parameters, so the baseline is 3. The description adds extra semantics by explaining how prefix controls depth ('go one level deeper') and how the returned cursor enables pagination, reinforcing the schema without repeating it verbatim.

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 folders/files directly under a folder in a user's connected bucket. It also names the downstream purpose (finding a storage://<id>/<path> job input) and notes that each entry carries a ready-made URI, which clearly differentiates it from a sibling like list_storage.

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?

Clearly frames when to use the tool: to discover paths for storage URI job inputs, and explains how to navigate deeper via prefix and paginate via cursor. It does not explicitly name alternatives or when not to use it, but the use case is specific enough for an agent to select it correctly.

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