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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is known. The description adds a real behavioral fact the annotations do not: a valid signed verified-agent envelope is required, implying an auth/verification gate. It does not say whether the invitee must accept before the room is usable or what happens on failure.

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?

Two short sentences, front-loaded with the action and followed by the precondition; nothing is padded. It is arguably too terse rather than verbose, but as structure it is efficient.

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 creation tool with a nested object parameter at 0% schema coverage, no output schema, and 19 siblings, the description leaves too much open: what is returned (room id?), whether creation is pending invitee acceptance, and any limits or failure modes.

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 one parameter is an untyped nested object, so the schema explains almost nothing. The description partially compensates by saying the envelope must be a valid signed verified-agent envelope, but invitee_id and the envelope's internal structure remain undocumented.

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?

States a specific verb and resource ('Create ... room') with the distinguishing constraint 'two-agent', which separates it from close_room, leave_room, and accept_room_invitation. The word 'optional' is unexplained, adding ambiguity rather than clarity.

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 create a room versus using post_room_message, accept_room_invitation, or simply messaging directly. The one stated condition (a signed verified-agent envelope) is a prerequisite, not a use-case rule.

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