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

With no annotations provided, the description carries the full behavioral burden and discloses nothing: not whether it is read-only, not what the guide contains, not its format, length, or whether it targets Kotlin-specific SDK usage. Nothing beyond the name is communicated.

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 phrase is short but that is under-specification rather than conciseness; it carries no front-loaded actionable content. A reader learns only that a guide exists, which the tool name already told them.

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 documentation/guide tool with no output schema and no annotations, the description must explain what the guide covers and when to consult it. It says nothing of the kind, leaving the agent unable to judge relevance against a dozen sibling guide-style tools.

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 'query' parameter is fully documented in the schema (100% coverage) as an optional topic to locate in the guide. The description adds no syntax, format, or example values, so baseline 3 applies per the high-coverage rule.

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 is essentially the tool name plus the parenthetical '(guide)', restating what the identifier already conveys. It does faintly signal that the tool returns documentation rather than performing the bootstrap itself, but that is the only semantic increment beyond the name.

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 routing among the many siblings that could plausibly overlap (room.flow.explain, room.lifecycle.plan, integration.plan, app.scaffold). The agent is left to guess entirely from the name.

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