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

The annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that the draft is 'owned' and lists returned state such as expiry, lock version, missing inputs, validation errors, and continuation state, but much of that overlaps with the output schema and does not disclose auth or failure behavior.

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?

The description is a single front-loaded sentence with no unnecessary preamble. It is somewhat dense due to the long list of returned fields, and the phrase 'without modifying it' is redundant with readOnlyHint, but overall it is efficient.

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 annotations and an output schema, the description provides sufficient scope and return context. The main omissions are sibling differentiation and explicit usage guidance rather than missing operational details.

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 only one parameter, draftId, and schema description coverage is 100%. The schema already documents it as the workflow draft ID, and the description adds no further parameter-specific semantics. Baseline 3 is appropriate when schema coverage is complete.

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 states a specific verb and resource: it returns the current owned workflow draft. It also names the draft scope and return content, so the operation is clear. However, it does not explicitly distinguish itself from related siblings such as get_workflow_plan, prepare_workflow_draft, or continue_workflow_draft.

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 explains what is returned but gives no explicit guidance about when to use this tool versus alternatives like continue_workflow_draft or get_workflow_plan. It also provides no exclusions or prerequisite conditions.

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