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

Annotations only say destructiveHint=true; the description goes further by explaining that archiving is non-destructive to operation (still runnable, scheduled, shared) and reversible via archived: false, plus surfaces the needs_confirmation/approvalId handshake. This is exactly the kind of behavior an agent cannot infer from the annotations.

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?

Four tight sentences with the scope constraint front-loaded, followed by the sibling exclusion, the archive semantics, and the confirmation caveat. No filler or redundancy.

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 an 8-param mutation tool with no output schema, the description covers scope, alternatives, partial-update expectation, archive reversibility, and the confirmation flow. Workspace/auth details are already in the schema, so nothing an agent needs to invoke correctly is missing.

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% and the schema already documents partial-set semantics for tags, archived true/false, and workspace auth rules. The description restates the field list and 'pass only what changes' but adds no syntax or format detail beyond the schema, 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?

Names the concrete resource (a Workbench flow) and the exact metadata fields it mutates (name, description, visibility, tags, archived), then explicitly excludes orchestration content and points to workbench_flows_edit_text. An agent can distinguish it from that sibling without opening either 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?

States when to use this tool versus workbench_flows_edit_text, tells the caller to 'pass only what changes' (partial update), and gives the condition for restoring a flow (archived: false). Alternative-routing and exclusions are both explicit.

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