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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds context they cannot carry: a human-confirmation requirement for remove/clear, a refusal condition (run in progress), and per-op semantics such as clear dropping readings on a watch list while keeping watched items. It stops short of saying whether anything is recoverable after a destructive op, which keeps it off 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?

Front-loaded with the core purpose, then op semantics, then constraints — nothing redundant. It is a single dense paragraph with stacked parentheticals, which costs some scannability but not correctness.

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?

With annotations covering the safety profile and an output schema covering returns, the description supplies what remains: op meanings, retention behavior, confirmation policy, and the in-progress refusal. Only the recovery/undo story is unaddressed for a destructive tool.

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 coverage is 80%, so the schema documents items, title, workflowId and keepHandled. The description's real contribution is decoding the op enum — add/remove behave differently on a watch list, skip_approval targets drafts awaiting approval, clear has list-type-dependent retention — meaning the enum values are unusable without it. It does not restate the item object shape, which the schema already covers.

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 with scope: change the work list a workflow keeps between runs. It explicitly distinguishes itself from the two nearest siblings — get_work_list (read) and update_workflow (change what the list records) — so the agent can route without opening a 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?

Enumerates every op with the condition that selects it, names the alternative tool for a related-but-different need (update_workflow), requires user confirmation for remove/clear, and states the tool is refused while a run is in progress. That is explicit when/when-not/alternatives coverage.

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