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

Annotations already establish this as a safe, non-destructive read, so the description's main contribution is the field preview (status, error, billing, job IDs), which hints at the polling/inspection use case. It adds no context on auth, rate limits, or staleness of workflow state, so the gain over the annotations is modest.

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?

One short sentence with the resource and lookup key front-loaded and the return fields compactly bracketed. Nothing here is redundant or padded.

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 single-parameter read with an output schema and safety annotations, the description covers purpose and expected payload adequately; return-value explanation is correctly offloaded to the output schema. Only the provenance and format of the required ID are left unaddressed.

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 description coverage is 0% for the single parameter, so the description must carry the semantic load. 'By ID' confirms workflow_id selects a specific workflow, but says nothing about the expected ID format or how to obtain a valid ID, adding only marginal meaning beyond the parameter name and title.

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 a specific verb and resource ('Get one transcription workflow') and narrows the scope to an ID lookup, with a parenthetical enumerating the returned fields (status, error, billing, job IDs). This implicitly separates it from transcription_list_workflows, though no sibling is named explicitly.

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 implied: use this when you already hold a workflow ID and need its current state. There is no explicit guidance on when to prefer it over transcription_list_workflows, nor any statement about prerequisites or where the ID comes from, leaving the agent to infer the routing.

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