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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether this is a read-only doc fetch, not what the guide covers, not how it differs from other swift::* guide tools. Absent annotations, this is a complete gap.

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 line is short and front-loaded, but its second half is an alias enumeration that conveys platform matching rather than tool behavior. Nothing is bloated, yet little of the text earns its place as invocation guidance.

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, and no parameter detail in the description, an agent cannot tell what bootstrapping guidance will be returned or when this guide is the right choice versus other swift::* planner/diagnose tools. For a guide-type tool the coverage is thin.

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 the single 'query' parameter is fully documented in the schema as an optional topic locator, so the baseline is 3. The description adds no parameter meaning beyond that (e.g., what topics are valid, behavior when query is omitted).

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 text names the resource (room.bootstrap) and platform (MediaSFU Apple/Swift) and parenthetically labels it a 'guide', but never states what the guide actually does or produces. It largely restates the tool name and title, so an agent learns platform routing but not the action.

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 differentiation from siblings like swift::room.flow.explain, swift::integration.plan, or swift::app.scaffold that likely overlap in the room-setup space. The alias list identifies the platform, not the usage condition.

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