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

Annotations already cover readOnly, idempotent, and non-destructive, so the 'Read-only' sentence adds little. However, 'the one offer to show' discloses that at most a single offer is surfaced, and 'Confirm is refused until every earlier step has been declined' reveals a cross-tool sequencing rule that is nowhere in the annotations or schema — genuinely useful behavioral context.

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 what is returned before the behavioral caveat. No filler, though the compressed phrasing of 'the one offer to show' takes a second read to parse.

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?

There is no output schema, so the description carries the burden of explaining the return value; it names the two returned pieces but not their shape or how a finished/abandoned flow is represented. For a one-parameter read tool this is adequate but leaves the agent guessing at edge-case 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 flow_id has 0% schema description coverage, so the schema contributes nothing about its meaning. The description implies the parameter identifies 'this cancel flow' and its step state, but never states the expected format or what happens with an unknown or completed flow id.

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?

The description names the resource (a cancel flow) and the exact payload returned: the current step plus the single offer to show. That is specific enough for an agent to distinguish it from account-, post-, or messaging-oriented siblings, but the verb is implicit ('the step this cancel flow is on') rather than stated as a retrieval action.

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 only implied by the 'Read-only' note and the framing as a state check. No sibling alternative is named and there is no explicit statement of when an agent should call this versus other flow-related operations; the confirm-sequencing sentence hints at workflow context but does not tell the agent when to reach for this tool.

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