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

The description discloses meaningful behavioral details beyond the annotations: it updates 'every active event compatibly' and 'returns authoritative conversation counters.' It also indicates the operation is reversible ('manually unread'), which aligns with destructiveHint: false. The caution about work status adds context. With sparse annotations, this description carries the burden well, though it could mention error scenarios or idempotency.

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 two sentences with no filler. The first sentence covers purpose and mechanics; the second provides a critical usage caution. Information is front-loaded and every sentence earns its place.

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 relatively simple mutation tool with two parameters, the description is fairly complete: it states scope, the reversible nature, side effects on events, and that it returns counters. It does not describe the output schema (but none exists), nor does it cover failure modes, but these are not critical for correct invocation. The caution about pending work adds operational context.

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 compensate. It implies that 'conversationIds' refers to the conversations to be marked and that the 'read' boolean controls read/unread state (via 'read or manually unread'). However, it does not explicitly state that read=true marks read and read=false marks unread, nor does it mention constraints like max 500 items (which is in the schema). The description adds some value by confirming the scope, but it falls short of fully explaining each parameter.

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 clearly states the verb ('mark') and resource ('your own conversations') and distinguishes between marking read and manually unread. It also specifies the scope ('your own') which differentiates it from any tool that might affect other users' conversations or notifications.

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 provides a clear conditional rule: 'Do not mark work read until acted on or handed on.' This is an explicit when-not-to-use guideline. It also implies the primary use case (marking read/unread after handling) and scopes access to one's own conversations. However, it doesn't mention alternative tools (e.g., mark_notification_read), but those are for a different resource, so the omission is minor.

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