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, and it discloses nothing—no indication of whether the tool produces a plan, reads config, mutates anything, or requires auth. This is a total absence of 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?

The text is short, but brevity here reflects under-specification rather than efficient structure—there is no front-loaded statement of purpose or value. Every possible sentence that would earn its place is missing.

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, and an undocumented enum parameter, the definition is wholly inadequate for an agent to invoke the tool correctly. Nothing compensates for the zero-information description.

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 parameter 'backendMode' has 0% schema description coverage and an enum of cloud/self-hosted/local, yet the description says nothing about its meaning or impact. The agent gets no help understanding when to pick each mode.

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 merely restates the tool name with a parenthetical tag '(security-guide)', offering no verb or resource explanation. An agent cannot tell what 'security.proxy.rooms' actually does or returns; the only hint is that it relates to security guidance.

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 reference to alternatives such as the sibling 'security.proxy.rooms' variants for other frameworks or shared::room.authority.plan. Usage must be entirely inferred from the opaque name.

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