Mark Conversations Read

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

Annotations already declare idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the batching aspect (multiple conversations in one call) and says nothing about partial failures, unknown IDs, or what the response reports — acceptable given annotations, but low added value.

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?

A single front-loaded sentence with no filler; every word carries meaning for such a simple tool.

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 one-parameter, idempotent, non-destructive mutation with documented schema and an output schema, the description is sufficient to call the tool correctly. Minor gaps around partial-failure behavior are mitigated by annotations and the output schema.

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% and the single conversation_ids parameter is fully documented as a list of IDs to mark read. The description contributes nothing beyond that, so baseline 3 applies.

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 (mark as read) and resource (conversations), and the word "multiple" signals batch semantics that distinguish it from a hypothetical single-conversation variant. However, it does not reference the closely related siblings (list_conversations, get_unread_count, get_conversation_details) to help an agent place it in the workflow.

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 explicit statement of when to use this tool versus alternatives, nor any prerequisites. Usage is only implied by the name, so the agent must infer that this follows a listing or unread-count call.

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