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: no auth requirements, no indication of whether it mutates proxy/room configuration, no side effects, no rate limits, no output shape. '(security-guide)' is too vague to count as disclosure.

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 brevity here is under-specification rather than conciseness — a single fragment that repeats the tool's own name. Front-loading is moot because there is no substance to front-load.

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 1-parameter tool with no annotations and no output schema, the description should explain purpose, usage and behavior, and it supplies none of them. An agent has essentially nothing to act on beyond the tool's 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?

Schema description coverage is 0% and the sole parameter, backendMode, is never mentioned in the description. Its enum values (cloud/self-hosted/local) are self-explanatory in the schema, but the description adds no meaning about what selecting a mode implies for this tool.

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 restatement of the tool name plus a platform prefix and a vague tag '(security-guide)'. It names no verb or resource being acted on, so an agent cannot tell what the tool actually does from the text alone. Only the dotted name hints at a proxy/rooms security concern.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the ~40 platform-variant siblings (shared::, angular::, flutter::, etc.). Nothing tells an agent when this Android-specific variant is the right choice versus the shared one.

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