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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered structurally. The description goes beyond that by disclosing the payload contents (status, timestamps, step-run timeline, approval decisions), which is genuinely useful since there is no output schema. It stops short of covering auth requirements or pagination, hence not a 5.

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, no filler. The returned-field inventory comes first and the routing guidance second, which is the correct front-loading for a detail-fetch tool. Every clause earns 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 no output schema and no output annotations, the description must tell the agent what comes back, and it does so concretely (status, timestamps, step timeline, approval decisions). Combined with the explicit sibling routing, an agent has everything needed to select and invoke this tool correctly.

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?

There is a single required parameter, runId, and schema description coverage is 100% ('WorkflowRun id.'). The description adds no format, source, or lookup guidance for that id, so the schema carries the full burden. Baseline 3 is appropriate.

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 and resource ('Full execution context for one workflow run') and enumerates what that context contains: status, started/finished timestamps, step-run timeline, approval decisions. It also explicitly distinguishes itself from the two similarly-named siblings, so an agent can route correctly without opening any schema.

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?

Names two concrete alternatives with the condition that selects each: 'PREFER list_workflow_runs to discover runs by workflow id or status' and 'PREFER list_workflow_approvals for the caller's own approval inbox.' That leaves the reader with a clear picture of when this single-run lookup is the right call versus the list tools.

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