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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write. The description adds genuinely new and important behavior: entries land UNCONFIRMED and require human confirmation in the room, which changes how an agent should reason about the write. It omits duplicate-handling and whether failed writes are retried, so not 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?

Two short sentences with zero filler; the action is front-loaded and the lifecycle caveat follows immediately. Every clause carries 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?

With no output schema, no nested objects, and thin annotations, the description carries real weight. It covers the confirmation lifecycle well but leaves all three parameters undocumented, which is the main gap for a tool an agent must call with correct field semantics.

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% for three parameters, and the description compensates for none of them. In particular supersedes_id is entirely unexplained — an agent cannot tell from either source that it links this decision to a prior one it replaces, and the distinction between body and rationale is left to inference.

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 precise verb and resource — 'Append a decision to the room's log' — which distinguishes it from read-oriented siblings like get_decisions and from post_update. It never names an alternative explicitly, but the resource and append semantics make the intent unambiguous.

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 says nothing about when to call this rather than post_update, ask_room, or search_memory, nor about prerequisites or required context. The second sentence describes an outcome (unconfirmed state) rather than offering selection guidance.

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