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

With no annotations provided, the description must disclose behavioral characteristics. It mentions 'whether the record is still intact', which hints at integrity but does not clarify what happens if the record is not intact (e.g., error vs. partial data). It also doesn't state whether this is read-only (likely) or requires any authentication or permissions, though the description 'Read' implies no mutation.

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, fairly dense sentence that front-loads the core listing of returned content. However, it could be more concise by breaking into two sentences (e.g., first what it returns, then the integrity note). It is not excessively long, but the final phrase about integrity feels tacked on.

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 single-parameter read tool, the description is relatively complete on the return content, but given there is no output schema and no annotations, it should provide more context on the response format, any error conditions, or the nature of 'private notes'. The missing parameter semantics further reduce completeness.

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%, meaning the parameter 'room_id' is entirely undocumented in both schema and description. The description fails to explain what 'room_id' is, its format, or its role in identifying the negotiation. Since there is only one parameter, the description should have at least mentioned that it identifies the negotiation.

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 explicitly states the verb 'Read' and the resource 'negotiation', and enumerates the specific content returned: entries in order, the offer, approval status, next steps, and private notes. This clearly distinguishes it from sibling tools like negotiation_list (listing negotiations) and negotiation_approve (acting on them).

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 clearly conveys that this is the tool to use when you want to read a negotiation's full state, including private notes. It does not explicitly name alternative tools or exclusions, but given the sibling set, the read vs. list vs. act distinction is implied strongly enough that an agent would infer when to use it.

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