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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is structured. The description adds valuable context beyond the annotations: deletion is immediate and permanent, it affects the room and every entry, and no token is needed because the accountable operator can always erase. This gives the agent a clear safety profile. It does not mention whether the room can be recreated or whether any confirmation is required, but the permanent wording covers the most important behavioral trait.

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 short sentences with no filler. The most important safety information (host only, permanent deletion) is front-loaded, and the token note is a useful operational detail. Every sentence earns its place.

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 destructive tool with two parameters and no output schema, the description covers the critical context: who may call it, what it destroys, and the permanence. It does not describe the return value or error cases, but with no output schema and a simple parameter set, the description is sufficiently complete for an agent to invoke it correctly. A small gap is that it does not explicitly say the room_id must be a room the caller hosts, though 'Host only' implies it.

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 100%, so the schema already documents both parameters. The description adds the 'Host only' constraint, which clarifies the room_id semantics, and the api_key parameter is already well described in the schema. The description does not add much beyond the schema, but the baseline of 3 is appropriate because the schema carries the parameter documentation burden.

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 states a specific verb ('Deletes'), a specific resource ('the room and every entry'), and a clear scope ('immediately and permanently'). It also distinguishes itself from siblings like continental_delete_message and continental_purge_messages by targeting the whole room rather than individual messages. The title 'Burn a room now' reinforces the destructive scope.

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?

The description explicitly says 'Host only', which is a clear usage condition, and notes that no token is needed. It does not explicitly name sibling alternatives or say when not to use it, but the host-only constraint and the permanent-deletion framing give an agent enough context to avoid using it on rooms it does not host or when only message-level deletion is needed.

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