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

With no annotations supplied, the description carries the disclosure burden and addresses the key non-obvious behaviors: permission boundaries, encrypted-room runtime requirements, and the warning not to infer permission from workspace membership. It does not detail error/idempotency behavior, but it covers the high-risk aspects.

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?

Three dense sentences, with the primary action and scope front-loaded and every sentence earning its place. No filler.

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 four-parameter mutation tool with no annotations and no output schema, the description covers purpose, permissions, encrypted-room requirements, and a critical security caveat. It is not exhaustive about return values or edge cases, but it is adequately complete for correct selection and invocation.

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 schema already describes room_id, agent_id, and connection, with 75% coverage. The description adds the crucial mapping for `present` (add vs remove), constrains agent_id to an existing workspace agent, and ties encrypted rooms to the creator's runtime, supplementing the schema's connection description.

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 names the exact operation ('Add or remove'), the resource ('existing workspace agent'), and the scope ('in one room only'). This distinguishes it from sibling tools like room_members or room_archive without needing to open the schema.

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?

It gives clear context for when the call is valid: standard rooms require room creator/account owner permissions, encrypted rooms require the creator's local encryption runtime. It does not explicitly name alternative tools, but it provides enough situational guidance and a caution against inferring permission.

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