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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description does add one useful behavioral fact that annotations cannot convey: the scope of the write is limited to the calling actor's unread count, not everyone's. It says nothing about permissions, side effects on other counters, or what the response looks like.

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 fragment with no filler, but the brevity is under-specification rather than efficiency; a few more words on the target conversation and token would cost little and remove real ambiguity.

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 no output schema and no schema documentation, the description carries too much of the burden and delivers too little. It omits the target resource, the semantics of the token parameter, and any indication of failure or return behavior.

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 both required parameters (conversationId and conversationToken) are completely undocumented in the schema. The description does not mention either parameter or explain the difference between an ID and a token, leaving the agent to guess how to construct the call.

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?

"Clear the actor unread count" names a specific verb and effect, so the agent can tell it apart from siblings like get_conversation or block_conversation. However, it never mentions the conversation, which is the actual target resource implied by both required parameters, and "actor" is unexplained jargon.

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 guidance, no exclusion versus siblings such as get_conversation, and no stated preconditions. The agent must infer that this is the tool to call when the user opens or views a conversation.

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