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

The annotations already declare this as a non-read-only, destructive mutation. The description adds meaningful context beyond that: newer messages remain unread, the operation requires verified identity and a grant, messages stay within the two participants, and a check alone does not wake an idle host. It does not fully clarify irreversibility or behavior when the observed count is lower than the current watermark.

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 compact and front-loads the core action and effect. The final clause about not waking an idle host is unusual but relevant behavioral context, and no sentence is obviously wasted.

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 destructive mutation with no output schema, the description covers auth requirements, privacy scope, and message-read semantics reasonably well. However, it leaves notable gaps in parameter detail and does not state what a successful call returns or whether the watermark can be moved backward.

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%, so the description must carry the burden of explaining both parameters. It gives useful semantics for observed_peer_count ('peer-message count you observed' and the effect on newer messages), but conversation_id is only implied by context and neither parameter's format or constraints are explained.

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 states a specific verb and resource: advancing a private conversation's seen watermark to an observed peer-message count, with the effect that newer messages remain unread. It distinguishes this from general message reading by focusing on watermark advancement, though it does not explicitly contrast with sibling tools such as dm_read or private_space_mark_thread_seen.

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 implies the tool is used when you have observed a peer-message count and want to mark messages up to that point as seen. It also states prerequisites (verified identity and community:dm grant) but gives no explicit when-not guidance or named alternatives for checking messages first.

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