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

With no annotations provided, the description carries the burden of behavior disclosure. The verb 'List' suggests a read-only operation, and 'bound visitor session' indicates a precondition. But the description does not state whether this tool has side effects, requires special permissions, or what happens with an invalid or unbound session.

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 with no filler or redundant phrasing. Every word contributes to the core meaning, making it easy to scan and quickly understand the primary operation.

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?

The tool has two opaque required parameters, no annotations, and no output schema, yet the description only gives a one-line summary. It omits parameter value semantics, return format, error behavior, and how this listing relates to action-taking siblings. An agent would still need significant additional inference to use this tool correctly.

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%, so the description must compensate for the undocumented parameters. It only hints at the concept of a 'bound visitor session' but does not explain that visitToken likely identifies the session nor that bridgeBindingProof proves the binding. This is insufficient for an agent to construct valid arguments confidently.

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 uses a specific verb ('List') and resource ('visitor rooms'), making the core operation clear. It is distinguishable from siblings like bursia_visit_enter_room and bursia_visit_send, though the term 'bound visitor session' is somewhat domain-specific and not elaborated.

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 'for a bound visitor session' implies a prerequisite: the tool should be called when a visitor session is already bound. However, the description does not explicitly state when to use this instead of alternatives like bursia_visit_info or bursia_visit_enter_room, nor does it mention any exclusions.

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