set_room_allow

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

The description goes beyond the annotations by specifying the exact destructive behavior: it replaces the entire allow-list rather than merging. It also discloses the authorization requirement ('Owner-signed only') and the nonce constraint, which are not present in the annotations.

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 entire description is one efficient sentence, with the core action and scope front-loaded, followed by the two critical constraints (replacement and nonce). There is no filler or repetition of schema content.

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 mutation with a nonce and authorization requirement, the description covers what is changed, the ownership precondition, the signing requirement, and the nonce ordering. The schema supplies parameter details and the annotations supply the read-only/destructive profile, so nothing essential is missing.

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 input schema already describes all five parameters (100% coverage), so the baseline is 3. The description adds value by clarifying that the dids parameter is the complete set of writers permitted in the room and by linking the nonce requirement to the claim transaction, reinforcing that the list is a full replacement.

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 identifies a specific verb ('Publish'), the resource ('allow-list for a room this identity owns'), and the effect ('replacing the previous list'). This clearly distinguishes the tool from siblings like read_room or list_rooms and from any delta-style update, leaving no ambiguity about what the tool does.

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 states the precondition that the room must be owned by this identity and the constraint that the operation is owner-signed with a nonce exceeding the one used by the claim. It does not explicitly name alternatives or give when-not-to-use conditions, but no sibling tool performs this allow-list replacement function, so the context is clear.

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