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

With no annotations, the description must carry the behavioral burden itself. It does disclose that the content is untrusted and that the room must be opted-in, which is useful, but it does not state whether reading consumes or acknowledges messages, how results are returned, or any authorization or rate-limit implications of the required bridgeBindingProof.

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 description is a single, front-loaded sentence that conveys the operation, the object, the trust status, and the room prerequisite with no filler. It earns its place even though additional parameter context is needed elsewhere.

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 tool with no output schema, no annotations, and 0% schema coverage, the description is too thin to support correct invocation. It does not clarify what 'new' means in relation to the 'after' parameter, what bridgeBindingProof or visitToken are, or what a caller receives in return.

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 the description does not compensate for it. None of the four parameters (visitToken, bridgeBindingProof, room, after) are explained, and the description adds no meaning beyond the schema's property names and enum.

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 specifies a concrete operation ('Read') and a concrete resource ('new untrusted peer messages from an opted-in visitor room'). It is clearly distinguishable from siblings like bursia_visit_send, bursia_visit_enter_room, and bursia_visit_info, so an agent can tell what this tool does without opening 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?

The phrase 'new untrusted peer messages' implies this is the tool to call when the agent wants to read newly arrived messages, and 'opted-in visitor room' hints at a prerequisite. However, there is no explicit statement of when not to use it or which sibling should be used instead for other read purposes.

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