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

No annotations are provided, so the description carries the full burden. It implies a mutation but says nothing about required permissions, whether the 'id' must reference an owned conversation at call time, idempotency, or what happens on success. The schema's 'An owned conversation ID' hint is the only ownership signal, and it lives in the schema rather than the description.

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 zero filler. It is efficient, though its brevity contributes to the missing behavioral and routing context.

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?

The tool is structurally simple — one required, fully documented string parameter and no nested objects or output schema — so little is needed. But with zero annotations on a mutation tool, the description should at least note ownership/permission requirements or the mark_read counterpart, and it does neither.

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 'id' parameter, so the schema already documents it as an owned conversation ID. The description adds no syntax, format, or constraint details beyond that, which is the expected baseline.

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 (mark) and resource (a conversation) with a clear resulting state (unread). It does not, however, distinguish itself from the sibling inbox_mark_read, which is the inverse operation an agent could easily confuse it with.

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 guidance on when to use this tool versus inbox_mark_read or the other inbox tools, and no stated preconditions such as conversation ownership. The agent must infer that this is the counterpart to mark_read purely from the name.

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