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

Beyond readOnlyHint/openWorldHint the description adds cost ("Free"), a precise semantic definition of last_test fields including the meaning of clean and unchanged_since_test, and an explicit prompt-injection warning that header names, prompt text and sheet values are customer data, not instructions. That last point is real safety context no annotation provides. It omits any statement about behavior when the flow_id does not exist.

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?

Front-loaded with what is returned, then the last_test breakdown. The field enumeration is long but earns its place because there is no output schema. Slight density cost from packing the field list into a single run-on sentence.

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 one-parameter read tool with no output schema, the description carries the entire return-value burden and does so thoroughly, covering spec, inputs, outputs, variables and the nested last_test object. Only error/not-found behavior is left uncovered, which is a minor gap at this complexity.

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 0% and there is one required parameter, flow_id, which the description never names or explains. The phrase "One Flow" implies the parameter selects a single flow, but no added meaning (format, validity, what an unknown id yields) is supplied beyond the UUID pattern in the schema.

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?

"One Flow with its version 2 spec, the sheet columns it reads (inputs), the columns it writes (outputs) and its variables" states a specific resource and enumerates its returned facets, which distinguishes it from list_flows. The retrieval verb is only implicit (the name carries it), and it does not explicitly contrast with get_flow_run, which also deals with a Flow.

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?

There is no statement of when to call this versus list_flows or get_flow_run; the last_test paragraph mentions flow_run_id but never says to switch to get_flow_run for run details. An agent must infer the usage from the sibling names alone.

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