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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing: not whether this is read-only or mutating, not whether it requires a configured room, not what it returns or how large the output is. A single-word alias does not cover that burden.

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?

It is short, but this is under-specification rather than conciseness — the single sentence is a namespace-qualified identifier plus an alias, carrying no actionable content. Brevity here is a symptom of missing information, not efficient writing.

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 annotations, no output schema, an undocumented enum parameter, and dozens of similarly named sibling tools, the description should do substantial work to orient the agent. It does none of it, leaving the tool effectively unselectable on any principled basis.

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 0%, so the description must compensate for the undocumented 'mode' parameter, and it says nothing at all. While the enum values (create/join/both) are somewhat self-explanatory, the description adds zero meaning about what each mode explains or when to pick one.

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 is essentially the tool name repeated with a parenthetical alias ('flow-explainer'), which only faintly hints that it explains room flow. There is no verb, no statement of what 'room flow' means, and no differentiation from siblings like room.bootstrap, room.lifecycle.plan, or runtime.diagnose. This is tautological restatement rather than a purpose statement.

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?

No when-to-use guidance, no prerequisites, and no mention of any alternative tool. The agent gets no signal about whether this belongs before bootstrap, after lifecycle planning, or how it relates to the many sibling room.* tools.

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