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

Annotations already declare non-read-only, non-idempotent, non-destructive, non-open-world. The description adds genuinely useful context beyond that: it is private state only, it never touches the shipped library or another trial, and it requires the sign-in session. It still doesn't describe what a successful call returns or any rate limits, keeping it from a 5.

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 sentences, with the sign-in prerequisite front-loaded before the action description. Each sentence carries useful information; there is minor density but no filler.

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 4-parameter, no-required-args mutation tool with no output schema, the description covers the key agent needs: auth/session flow, the effect of the call, and the scope limitation of the state change. It is essentially complete, missing only return-value or error behavior that the absent output schema would otherwise cover.

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 100%, so the schema already documents session, trial_id, published (true=ready/false=draft) and workflow_id. The description's phrasing ('mark ... ready or draft') mirrors rather than extends the published semantics, so the baseline 3 applies.

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+resource: it marks a private playbook in this trial as ready or draft. It also draws a boundary that separates it from content-creating siblings (save_workflow/delete_workflow) by noting publishing 'never adds content to the shipped library.' It doesn't name a sibling explicitly, so it falls just short of 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?

It clearly states the prerequisite (call connect/connect_verify first unless already signed in) and the two states the tool can set. However, it gives no explicit guidance on when to use this versus save_workflow or deleting/re-creating a workflow, leaving that choice to inference.

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