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

Annotations are absent, so the description carries the full behavioral burden, and it discloses nothing: no return format, no side effects, no auth or environment prerequisites, no indication whether it emits code, prose, or configuration. '(guide)' is the only signal and it is too thin to act on.

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 comes from under-specification rather than economy. There is no front-loaded statement of purpose, just a namespace fragment, so nothing meaningful is communicated in its single clause.

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 cross-platform bootstrap tool with no annotations and no output schema, the definition leaves an agent with no basis to know what it produces or when to call it. Nothing an agent needs in order to invoke it correctly is present.

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 optional 'query' parameter is fully documented in the schema (100% coverage, maxLength 500), so the schema already does the work. The description adds no meaning beyond it, which is the baseline case for high schema coverage.

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 'MediaSFU Android :: room.bootstrap (guide).' is essentially a restatement of the tool name plus the platform namespace. Only the parenthetical '(guide)' hints at the resource type (a documentation lookup), but there is no specific verb or outcome that distinguishes it from siblings like room.flow.explain 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?

No guidance whatsoever on when to invoke this versus the ~120 sibling tools, including the closely named room.flow.explain, integration.plan, or app.scaffold. The reader cannot infer whether this is a first step, a fallback, or a reference lookup.

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