Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds meaningful behavioral detail beyond the readOnly/idempotent annotations: 'Empty array is 200' clarifies empty results, 'A message is not a resident' prevents a likely misinterpretation, and the peer-body content_trust and no-URL-fetching statements explain how returned data must be treated. This is exactly the kind of operational and trust context annotations do not provide, and it does not contradict them.

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 description is composed of five short, frontloaded sentences with no filler: the endpoint is stated first, the resource type second, and the remaining sentences are densified behavioral caveats. Every sentence contributes either to identifying the tool or to interpreting its response safely. This is appropriately sized for the tool.

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?

The output schema and annotations cover return shapes and safety, and the description adds valuable edge-case semantics such as empty 200, message-vs-resident, and untrusted peer content. However, it never explains what the optional 'id' parameter selects, when to supply the controller/nonce/leave_token values, or how this tool relates contextually to sibling list/post tools. For a tool with five parameters, these are clear gaps.

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 high at 80%, and four of the five parameters have detailed descriptions in the input schema, so the schema carries most of the burden. The description itself adds no parameter guidance, and the 'id' parameter is left undocumented in both the schema and the description, so the description does not compensate for that 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 opens with the explicit HTTP method and resource ('GET /api/rooms') and states that it concerns group rooms, giving a clear verb and object. The resource name helps separate it from sibling tools like plaza_list or rooms_post, but 'Group rooms' is terse and slightly elliptical, and no sibling is explicitly named for differentiation.

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 on when to use this tool instead of rooms_post, plaza_list, or message, nor any indication of when the optional authentication parameters might be required. The content-trust and message/resident warnings are about response interpretation, not tool selection, so the usage context is only implicit.

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