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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds a small amount of value by characterizing the payload as a mix of observed outcomes versus inferred expectations, which flags that some returned data is model-inferred rather than captured. It does not mention permission needs, size limits, or failure modes for a missing flowId, so it does not go far beyond the annotations.

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?

A single front-loaded sentence with the verb and resource first and zero filler. It is appropriately short, though the terseness is part of why usage guidance is absent.

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 and full parameter documentation, the description need not explain return values or argument formats, and the annotations cover safety. The remaining gap is workflow context: for a detail-fetch tool gated on a flowId from list_flows, one clause on the list-then-get sequence would make it complete.

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% and each parameter carries substantive documentation, including the version-pinning rule ('do not use latest as an alias') and the environment omission rule. The description adds nothing parameter-level, so the baseline of 3 would apply, but the structured fields are unusually strong here rather than merely adequate.

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?

Clear specific verb plus resource plus scope: 'Read one user flow', which distinguishes it from the family of list_* siblings such as list_flows and list_replays. It also names the payload contents (observed outcomes, inferred expectations, scoped evidence), so an agent knows it is the detail-fetch counterpart to the list tool. It stops short of explicitly naming list_flows as the source of the ID, which is what would separate it from a 5.

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?

The description gives no when-to-use, when-not-to-use, or alternative routing guidance. The only workflow hint ('Exact flow ID returned by list_flows') lives in the parameter schema, not the description, and nothing tells the agent how get_flow differs from sibling detail tools like get_scenario_manifest or get_page_summary.

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