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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful context with 'with access checks' and 'including unpublished work', but it does not explain access-check failure behavior or the shape of the returned draft.

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 redundant or wasted wording. It communicates the core read operation and scope immediately.

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 simple one-parameter read tool with rich safety annotations, the description covers purpose, access checks, and unpublished scope. However, with no output schema it does not clarify the returned draft structure, and workflow_id sourcing remains undocumented.

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?

The schema has 0% description coverage for the sole workflow_id parameter, and the description only refers to 'a workflow' without explaining ID format, source, or constraints. The parameter name is self-explanatory, which prevents a 1, but the description does not compensate for the schema 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 the specific verb 'Read' and the resource 'workflow and its current editable definition', and adds 'including unpublished work' to distinguish it from a published-workflow read. It does not explicitly name sibling alternatives such as get_workflow or list_workflow_drafts, so it falls short of a 5.

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?

The description gives no explicit when-to-use or when-not-to-use guidance and does not route the agent between this tool and alternatives like get_workflow or list_workflow_drafts. 'Including unpublished work' hints at draft scenarios but is not enough to constitute usage guidance.

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