List workflow files

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, yet the description still adds real behavior: an empty list rather than an error for workflows that never stored a file, and that readPath is a download URL template. Pagination via cursor is also disclosed; rate limits or auth needs are not mentioned.

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 sentences, front-loaded with the resource scope, then return fields, then the empty-list and paging caveats. No filler and no repetition of the title.

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?

An output schema exists and the description still summarizes the returned fields (key, size, last-modified) plus the readPath template, so an agent has enough to call and interpret results. Minor omission is any note on permission/auth requirements for the storage bucket.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining the purpose of readPath and the cursor round-trip. It does not elaborate on limit bounds, which the schema already covers.

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 (List) and a precisely scoped resource (the files a deployed workflow's runs stored in its own storage bucket in the user's Cloudflare account). That scope cleanly separates it from siblings like list_workflow_versions or list_runs without needing to name them.

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?

Usage is implied by the scoping ('deployed workflow's runs') and paging guidance says to pass cursor back, but there is no explicit when-to-use/when-not-to-use statement or named alternative for retrieving a single file's contents versus listing.

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