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 does add value by naming the fields returned (state, turn, nearest deadline), which matters since there is no output schema, but it says nothing about ordering, pagination, or the effect of the room_tokens scope.

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 compact fragment with zero filler, front-loading the resource and the three payload fields. Nothing could be trimmed without losing information.

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?

Because there is no output schema, the brief return-field summary is helpful, but key facts are missing: the required room_tokens input bounds the query to at most 20 requested rooms, which sits awkwardly against the 'Your negotiation rooms' phrasing implying a full listing, and ordering/pagination are unstated.

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 both room_tokens and include_closed are already documented in the schema; baseline is 3. The description adds no syntax, limit, or behavior detail beyond what the schema states.

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?

Names the resource (negotiation rooms) and the three data points returned (state, whose turn it is, nearest deadline), so an agent knows this is an overview/listing tool. It never states a verb like 'list' and does not differentiate itself from siblings such as negotiation_read, so it falls 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 when-to-use guidance, no exclusions, and no mention of alternatives like negotiation_read or negotiation_join. The possessive 'Your negotiation rooms' only loosely implies a status-check use case.

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