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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses that access/permission checks are performed and that unpublished draft content is returned – behavior the annotations do not convey.

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 no filler; the key action and scope come first. The trailing qualifiers ('with access checks, including unpublished work') are dense but each carries distinct information.

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 tool whose annotations already cover the safety profile and which has no output schema to explain, the description supplies the essential behavioral context (access checks, draft inclusion). The main omission is any explicit routing versus sibling read tools, which is a minor gap.

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?

Only one parameter (workflow_id) with 0% schema description coverage, and the description adds no format, constraint, or source guidance for it. The name is largely self-explanatory, so it is adequate, but it does not compensate for the coverage gap.

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 (Read) and resource (a workflow and its current editable definition), and adds the scope qualifier 'unpublished work' plus 'access checks'. This distinguishes it reasonably from the published-version-oriented get_workflow and the list-style list_workflow_drafts, though it never names those siblings 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 by 'editable definition' and 'including unpublished work' – an agent can infer this is for draft, not published, content. But there is no explicit statement of when to prefer this over get_workflow or list_workflow_drafts, and no prerequisites beyond the vague 'access checks'.

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