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: no indication of whether this reads or mutates, what auth is required, whether it contacts a proxy service, or what it returns. For a tool whose name contains 'security.proxy' this is a complete gap.

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 and not padded, but it is under-specified rather than concise — a single title-echo line that conveys no information beyond the tool name. Brevity without content does not earn credit here.

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, an undocumented parameter, and no explanation of the security/proxy concept, the definition is entirely inadequate for an agent to call this tool correctly or to distinguish it from its many platform-scoped siblings.

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 description adds no meaning for the single 'backendMode' parameter. The enum values (cloud, self-hosted, local) are self-explanatory, but nothing explains the default, the consequences of each mode, or whether it is required.

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 a restatement of the tool name with a platform prefix and the parenthetical '(security-guide)'. 'security.proxy.rooms' is an opaque dotted identifier; the text never states a verb or explains what the tool actually produces or does. The '(security-guide)' hint is the only semantic signal, so it lands just above pure tautology.

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, when-not-to-use, or alternative guidance of any kind. With ~140 sibling tools available, including near-identical 'security.proxy.rooms' variants for every other platform and a 'shared::security.proxy.rooms', an agent has no basis for choosing this one over them.

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