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

Goes well beyond the annotations by disclosing the human-confirmation gate ('only their answer releases the move'), the irreversible consequence of reject, the quorum rule (both parties approve the same hash), and the common_ground exception where it 'goes out at once.' This is strong added context for a destructive, non-idempotent tool; only the absence of any note on failure modes (bad/stale hash, wrong room state) keeps it off a 5.

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?

Front-loaded with the action, then the confirmation mechanics, then the sibling alternative and the edge case. Dense but nearly every clause carries operational information; the phrasing is a bit packed into one paragraph, which slightly hurts scanability.

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 3-parameter destructive tool with no output schema, the description covers the decision semantics, the confirmation flow, the quorum condition, and the irreversibility of reject. What it lacks is what the caller gets back on success/failure and how stale or mismatched hashes are handled.

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?

With only 33% schema description coverage, the description carries real weight: it explains that approve must quote a subject_hash obtained from negotiation_read, and that reject needs no hash. The 'room' parameter's expected value/format is left implicit, which is the one remaining gap.

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?

States a specific verb pair (accept/decline) and the exact resource: the terms on the table. It is immediately distinguishable from siblings such as negotiation_propose (keep negotiating) and negotiation_cancel, so an agent can route without opening any schema.

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?

Explicit when-to-use and when-not-to-use: 'reject closes the room for good; to keep negotiating, counter with negotiation_propose instead.' It also names the prerequisite (subject_hash from negotiation_read) and the alternative flow for common_ground rooms.

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