Mark conversation read

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

The description adds behavioral detail beyond the annotations by specifying that the operation affects every message and clears the unread badge. The annotations already indicate a non-read-only, idempotent, non-destructive mutation, and the description aligns with those signals without contradicting them.

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?

One concise, front-loaded sentence conveys the action, scope, and effect with no filler. Every word contributes to understanding the tool's behavior.

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 simple, single-parameter mutation tool with an output schema and annotations covering idempotency and destructiveness, the description is complete. The only potential gap is not naming sibling tools, but that does not hinder correct invocation.

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% for the single required parameter, conversation_id, which is already described as 'Conversation id'. The description does not meaningfully add parameter-level semantics, so the baseline of 3 is appropriate.

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 uses a specific verb ('mark'), defines the scope ('every message in one conversation'), and states the observable effect ('clearing its unread badge'). It clearly differentiates this from notification-level read tools by anchoring the action to a single conversation.

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 gives a clear context for use: when the goal is to clear the unread badge for all messages in a conversation. It does not explicitly mention alternatives such as mark_notifications_read, so it lacks explicit when-not-to-use guidance, but the intended usage is unambiguous.

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