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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the substantive behavioral fact that this artifact is only meaningful post-room and enumerates its sections, but says nothing about what happens if called mid-room or what errors/auth failures look like.

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 tight sentence that front-loads the timing condition and the returned contents with no filler. It reads as a sentence fragment, which is efficient but leaves the action verb to 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 usefully enumerates the brief's contents (agreed terms, authority, assumptions, escalations, ledger head), which is the right move. However, it leaves the room_id parameter, the link-vs-id selection, and pre-room behavior unexplained, so it is only adequate for a 2-parameter secure lookup.

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 coverage is only 50%: 'link' is documented as a secret seat link, but 'room_id' is undocumented in both schema and description. The description adds no parameter meaning at all and does not clarify whether link, room_id, or neither is needed despite zero required parameters.

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 resource is named precisely ('The decision brief') and the timing qualifier 'once the room has ended' distinguishes it from the live-state siblings get_room and wait_for_turn. It stops short of a verb (the title supplies 'Read'), so it is clear but not fully self-contained.

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?

'Once the room has ended' is an implied precondition that tells the agent when this tool is valid, but no alternative is named for when the room is still open, and no guidance is given for a room that never ended or a failed lookup.

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