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 — no explanation of what a 'flow explain' returns, whether it is read-only, whether it requires an existing room/project context, or how expensive it is.

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?

The text is brief, but it is under-specified rather than concise: the only content is a title echo and an alias list, so no sentence earns its place by conveying usable information.

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 tool with a parameter, no annotations, and no output schema, the description supplies none of the missing context — not what is explained, not the expected input, not the return shape. An agent cannot reliably invoke it from this definition.

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?

The single 'mode' parameter has an enum (create/join/both) but 0% schema description coverage, and the description adds no semantics for it. It is unclear whether mode scopes the explanation to a create flow, a join flow, or both, and nothing compensates for the schema gap.

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 only restates the tool name and its aliases ('room.flow.explain (flow-explainer). aliases: unity, unity-sdk, csharp-unity'). It never states what the tool actually does or what it returns, leaving the verb 'explain' to be inferred from the name alone, with no differentiation from siblings like room.bootstrap or integration.plan.

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?

There is no guidance on when to use this tool, when not to, or which sibling tool to pick instead. The 'aliases' line points at naming variants, not at selection criteria, so an agent has nothing to route on.

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