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. It adds nothing about what the command does, whether it mutates state, what permissions are needed, or what happens when run (the dry-run/execute distinction is only in the schema, not the description).

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 description is a single fragment that is under-specified rather than concise; it lacks any front-loaded explanation of purpose or behavior. It is not verbose, but it wastes the opportunity to inform.

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 command tool with no annotations and no output schema, the description should explain what bootstrap does, what it creates or modifies, and any prerequisites. It provides none of this, leaving the agent unable to judge the tool's effect or appropriate use.

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 schema has 100% description coverage for both parameters (execute and projectRoot), so the baseline is 3 even without description help. The description adds no additional meaning about parameter semantics.

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 restates the tool's name ("MediaSFU Vue :: room.bootstrap") with the added tag "(command)" but never states what the tool actually does. It gives no verb or resource beyond the name, making it tautological rather than a clear 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?

There is no guidance on when to use this tool, what prerequisites it requires, or how it differs from the many sibling bootstrap tools (e.g., shared::room.bootstrap, android::room.bootstrap). It offers no context for selection.

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