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

Annotations only declare the generic safety flags (not read-only, not destructive, not idempotent). The description adds real behavior beyond them: the result is an immutable revision, no run is started, no compute is spent, and user approval is a gating condition. It stops short of stating what happens on a repeated publish or when expectedDraftVersion is stale.

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?

Three short sentences, front-loaded with the action, followed by the negative scope and the precondition. Every sentence earns its place with no padding.

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?

Behavioral context is solid for a non-idempotent mutation, but with 0% parameter coverage and no output schema, the agent is left without guidance on what expectedDraftVersion must match or what a successful publish returns. Adequate but with clear gaps.

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% and both parameters are required, so the description carries the full explanatory burden. It says nothing about workflow_id or expectedDraftVersion, leaving the optimistic-concurrency semantics of the version parameter entirely undocumented.

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 and resource ('Validate and publish the current draft as an immutable revision') and immediately delimits scope against the run-oriented siblings ('Does not start a run or spend compute'). An agent can separate this from validate_workflow and start_workflow without opening any schema.

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?

Gives an explicit precondition: 'Publish only after the user has approved the intended workflow.' It also rules out run execution, which is useful context. It does not, however, name alternatives such as validate_workflow for a dry check or update_workflow for editing the draft.

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