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, yet it discloses nothing: not whether the tool mutates state or emits a plan, not whether it needs credentials, not what the two enum modes change. The name implies it is a planner, but the description supplies zero 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 this is under-specification rather than conciseness — a single fragment that spends its whole length repeating the tool name. There is no front-loaded statement of purpose because no purpose is stated at all.

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, 0% parameter coverage, and two enum parameters whose semantics are unexplained, the description is wholly inadequate for an agent to select or correctly invoke this tool within the large shared:: family.

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 description coverage is 0% for both parameters, and the description adds nothing about `operation` (create/join) or `backendMode` (cloud/self-hosted/local). The agent gets no meaning for either parameter beyond raw enum values, so the description fails to compensate for the coverage gap.

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 a tautology: it only restates the tool name and its alias ("room-authority-planner") plus the "mediasfu-shared" namespace. There is no verb describing what the tool actually does (e.g., produce a plan for room authority/permissions) and no differentiation from siblings like shared::room.lifecycle.plan or shared::security.proxy.rooms.

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, when-not-to-use, or alternative-tool guidance is given. The agent cannot tell from the text whether this planner should be invoked before room.bootstrap, alongside security.proxy.rooms, or at all — there is simply nothing to route on.

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