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

Annotations only say it is a non-destructive, non-open-world write. The description goes well beyond that by disclosing preconditions (flow must be workspace-shared and published) and the human-in-the-loop behavior: it may return a needs_confirmation envelope, and the agent must state which flow and why and wait for approval. That is exactly the extra context the annotations cannot carry.

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 tight sentences, front-loaded with what it does, then prerequisites, then the approval caveat. Every clause carries information; nothing is repeated from the title or schema.

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 no output schema, the description does the work of explaining the one non-obvious return shape (needs_confirmation). All four parameters are covered by the schema. Minor gaps remain: no mention of what happens if the flow is unpublished, or whether adding an already-present flow errors or is idempotent.

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 flowId, roomId, workspace and approvalId are already fully documented in the schema (including the personal-token workspace rule). The description adds no format, constraint, or default information beyond what the schema provides, 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?

States a specific verb+resource (adds a Workbench flow to a room) and immediately clarifies the effect ('as a member, so people can @mention it'). That framing distinguishes it from sibling mutations like rooms_post or workbench_flows_share_create without needing the 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 explicit when-to-use triggers ('after building a specialist flow for a room's work, or when someone asks for a flow to join') plus hard prerequisites (flow must be shared with the workspace and published). It never names a sibling alternative or a when-not-to-use case, so it falls short of a 5.

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