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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true. The description adds meaningful beyond-annotation detail: the room becomes read-only and is deleted after its TTL, and last_message is posted before the effect. It doesn't state auth/permission failure behavior, but the two-stage lifecycle is valuable 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?

Two tight sentences front-load the host restriction and the effect, then the last_message timing. Every clause carries information; 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?

Covers authorization, the two-stage lifecycle (read-only then TTL deletion), and last_message ordering. No output schema exists, but a close operation has little return surface. Missing only failure/permission-error behavior, a minor gap for a well-annotated destructive tool.

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 coverage is 67%. The description adds semantics for last_message (posted first, with example content), which the schema leaves undocumented. token and room_url are covered by the schema descriptions, so the description fills the meaningful 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?

States a specific verb (ends/closes) and resource (the conversation/room), plus the authorization scope ('Host only'). This distinguishes it clearly from siblings like parlor_post or parlor_read, which act on the open room.

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?

Specifies 'Host only', an explicit eligibility constraint, and implies the alternative workflow with the last_message example ('continued at NEW_ROOM_URL'). It doesn't name a sibling to use instead or state when-not-to-close, but the host restriction and handoff example give clear context.

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