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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds behavior the annotations and schema do not: newest-first ordering and the directive "never guess" an upload_id. That is meaningful added context beyond the structured fields, though it omits anything about paging 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, front-loaded with the identity of the resource, then the trigger, then the row contents. No padding or redundancy; every clause earns its place.

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?

With an output schema present, return values need not be spelled out, and annotations already cover the safety profile. The description supplies the one thing neither structured field provides — when to call it and why — so an agent has everything needed to select and invoke 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 description coverage is 100%, so both parameters are already documented in the schema (workflow_id sourced from list_workflows, limit meaning). The description reinforces the upload_id/workflow_id correctness rule but adds no syntax or format detail beyond what the schema carries, making the baseline 3 appropriate.

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 ("The script files a workflow can already read") plus an ordering guarantee ("newest first"). It distinguishes itself from the upload siblings by framing the files as things the workflow has *already* been given, rather than a generic file listing.

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?

Gives an explicit trigger: "Call it after the user uploads one in the browser, to learn its upload_id." That is clear when-to-use context with a stated goal. It stops short of naming an alternative or a when-not condition, so it is strong but not exhaustive.

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