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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing: no read/write nature, no side effects, no prerequisites, no output format, no rate limits. Calling it a "guide" does not substitute for behavioral context.

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 that brevity reflects under-specification rather than disciplined conciseness. The only content is a name echo plus aliases, so nothing substantive is front-loaded.

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 guide-lookup tool with no output schema and no annotations, an agent needs at least a hint of what topics the guide spans and when to invoke it. None of that is present, leaving the definition unusable for correct selection.

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% and there is a single optional parameter whose description ("Optional topic to locate in the guide") is already fully documented. The description adds nothing about the query parameter, so the neutral baseline of 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?

"MediaSFU Unity :: room.bootstrap (guide)" only restates the tool name and adds the word "guide"; it never states what room.bootstrap actually does or what the guide covers. It gives no verb-plus-resource explanation that would distinguish it from unity::room.flow.explain or unity::integration.plan. The alias list is metadata, not purpose.

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 statement of when to use this tool, when not to, or how it differs from the dozens of sibling unity::* tools (room.flow.explain, integration.plan, env.preflight, etc.). An agent has no basis for selecting it over any neighbor.

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