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

Annotations already declare the read-only, non-destructive, closed-world profile, so the description only needs to add beyond that — and it does: result ordering, the visibility rule that Final staff additionally see Final's own flows marked owner: "Final", and the presence of an upstreamUpdate field on clones. It stops short of mentioning pagination or whether limit truncates the list.

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 core action and scope, then the special-case visibility rule, then the follow-up routing. Dense but every clause carries information; the upstreamUpdate sentence is slightly tangential but still actionable.

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 no output schema, the description does the work of naming returned fields (id, title, timestamps, live theme knobs, upstreamUpdate) and the owner marker, which is exactly what an agent needs to consume the result. The remaining hole is the undocumented limit/pagination behavior.

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?

The single parameter (limit, 1-100) has 0% schema description coverage and is never mentioned in the description. The "newest first" phrasing hints at ordering but gives no guidance on what limit controls or how to page through a large result set, so the description fails to compensate for the schema gap.

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+resource ("List the flows (app builds)") and pins the scope to the caller's organization with an ordering guarantee ("newest first"). It also names the fields returned and clarifies the special-case owner value, so an agent can distinguish it from flow_create_flow and the flow_read/write file tools without opening schemas.

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?

It routes the agent forward explicitly: "Use a flow id with the other tools, or create_flow to start fresh," and points clones at get_upstream_update / apply_upstream_update. That covers when to use this result and what to do next, but there is no explicit statement of when not to call it (e.g. a search/filter alternative).

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