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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully adds what the read returns (history plus live terms), but says nothing about volume, pagination, or what happens with an invalid/stale room_token.

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?

A single short sentence, front-loaded with scope ('One room in full') and then the payload contents. No filler, no repetition of the title.

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?

With no output schema, the description does the useful work of telling the agent what comes back, which is the main thing it needs. However, for a tool that returns an entire negotiation history it omits response-size/pagination expectations and any usage context relative to the mutation siblings, leaving clear gaps.

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 single room_token parameter is already fully documented in the schema (100% coverage), including where it comes from (negotiation_open/negotiation_join). The description adds no format, validation, or error semantics beyond that, so the baseline 3 applies.

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 names the resource and its full contents — 'current state, every round, the terms on the table' — which is specific enough to distinguish it from a list-style sibling. The verb is implicit rather than stated, and nothing explicitly contrasts it with negotiation_list, so it stops short of a 5.

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?

There is no statement of when to call this versus negotiation_list or the mutation tools (propose/respond/cancel). An agent must infer that this is the inspection step before acting, but the description never says so.

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