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, and it discloses nothing about read/write nature, permissions, side effects, or output. The single parenthetical adds no 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 the brevity reflects under-specification rather than efficient conciseness; it is a name-and-namespace label with a tag, not a front-loaded informative statement. Every word is technically 'spent' but none conveys actionable meaning.

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 tool with a mode-selecting parameter, no annotations, and no output schema, the description is entirely inadequate. An agent has no information to invoke it correctly beyond guessing from the name.

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 sole parameter backendMode has 0% schema description coverage and an enum (cloud/self-hosted/local), yet the description never mentions it or explains what the modes select. With no schema documentation to fall back on, the description fully fails to compensate.

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 Kotlin :: security.proxy.rooms (security-guide)' merely restates the tool name and namespace without a verb or explanation of what the tool actually does. It gives no clue whether this explains proxy setup, lists available rooms, or configures security, so an agent cannot distinguish it from siblings on the basis of the text.

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 whatsoever on when to use this tool versus alternatives, and no conditions, prerequisites, or exclusions are stated. The '(security-guide)' fragment implies a documentation-style tool but does not tell the agent when to reach for it.

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