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

Annotations already establish this is a non-destructive, non-open-world write. The description adds value beyond them: the required preconditions (shared + published) and the fact that it 'may return needs_confirmation', with the expected agent behavior of stating the flow and reason and waiting for approval. It stops short of describing the success result or idempotency.

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 with the core action front-loaded, followed by prerequisites and the confirmation clause. No filler or repetition of the 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?

For a no-output-schema mutation tool with full annotation coverage, the description supplies the prerequisites, usage triggers, and the confirmation workflow an agent needs to call it correctly. It leaves the post-success state and any room-membership side effects unstated, but the essential gaps are covered.

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 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the needs_confirmation/approval path, which contextualizes the optional approvalId parameter and how the two-required-param call behaves on confirmation.

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 ('Adds a Workbench flow to a room as a member') plus the concrete effect ('people can @mention it and it can work on things with you there'). This clearly differentiates it from nearby mutation siblings such as rooms_post or rooms_start_agent_work.

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 triggers ('after building a specialist flow for a room's work, or when someone asks for a flow to join') and prerequisites (flow must be shared with the workspace and published). It does not name a competing alternative tool, but no obvious sibling overlaps this operation.

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