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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the safety profile is covered; the description adds the actual state change (unread count zeroed) and the return payload `{ ok: true }`, which no output schema provides. It stays silent on failure behavior for an unknown conversation id and on why idempotentHint is false when repeated calls appear to converge to the same end state.

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 clauses, front-loaded with the effect before the return contract; nothing is wasted. The phrasing 'goes to nothing' is slightly informal where 'zero' would be sharper, but it costs no clarity.

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 two-parameter mutation with full schema coverage, the description supplies what the schema cannot: the resulting state change and the response shape. Only edge cases (invalid ids, permission requirements) are absent, which is minor at this complexity.

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 100%, with both `campaign` (slug or id) and `conversation` (id or `table`) fully explained in the schema, so the baseline applies. The description adds no further meaning about parameter formats or the special `table` value.

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 names the resource (one conversation) and its concrete effect (unread count goes to zero), which tells an agent exactly what the call accomplishes. It does not differentiate from nearby siblings such as mark_notifications_read or read_conversation, so an agent must infer the boundary itself.

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?

There is no when-to-use or when-not-to-use guidance, and no named alternative. The agent is not told how this differs from read_conversation or mark_notifications_read, nor whether it is a per-conversation complement to a bulk mark-read operation.

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