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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds a genuine scope constraint the annotations cannot express: the interview transcript is deliberately excluded from the result.

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?

Two sentences: the usage trigger first, the exclusion second. No restatement of the name, no filler, nothing that fails to earn 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, the return shape need not be enumerated, and the annotations carry the safety semantics. The only residual gap is that the description never clarifies what identifiers are valid beyond the schema's uuid pattern.

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 0% and the single workflowId parameter is documented only by its uuid format, not by description text. The obligation to identify which workflow's ID to pass is left entirely to the caller's inference from the surrounding context.

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 pair (retrieve a single saved workflow) and enumerates the payload (map, effort, scores, open questions), which implicitly separates it from list_workflows and list_workflow_questions. It stops short of naming a sibling to route against, so it lands just under the top tier.

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?

"Use this when the user wants one saved workflow's..." gives an explicit usage trigger, and "Never returns the interview transcript" supplies a negative boundary. It does not, however, point to the alternative tool for transcript or list cases, so the when-not side is only half-covered.

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