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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still earns credit for a genuine behavioral warning beyond the annotations: that pending, applied and failed are distinct states and that a pending job is not complete, which prevents premature success reporting. It does not say what happens for unknown or expired ids, or whether repeated reads are cheap enough to poll.

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, zero filler, and the core capability is front-loaded ahead of the state caveat. Every clause carries information the agent needs and nothing is repeated from the title or annotations.

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 read-only status tool with full annotation coverage and no output schema, the essentials are present, but the tool takes a nested `input` object with four identifier fields and the description gives no guidance on which one identifies the job. Nothing about the returned state shape is needed (no output schema), but the invocation ambiguity keeps this at minimum-viable.

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 75%, so the schema carries most of the load, but the description adds meaning by naming the state kinds that the `kind` parameter selects from. It does not, however, explain how to choose between `id`, `key`, and `tool` inside the nested `input` object, nor does it mention the 'operation' kind present in the enum, leaving the identifier-selection question unanswered.

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 uses a specific verb ('Reads') with a clearly enumerated resource set ('background job, publication, action or workflow state') that maps onto the schema's `kind` enum. An agent can tell it is a status/state reader rather than a lister or mutator. It stops short of naming a sibling (e.g. workflows_list for enumeration), so it is clear but not sibling-differentiated.

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: the agent must infer that this is the tool to call after launching or triggering an async job. There is no explicit 'use when…' clause, no statement about polling cadence or when to give up, and no pointer to workflows_list/workflows_preview as the alternative for enumerating or previewing rather than checking state.

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