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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds genuine context beyond that: it discloses the exact mutation performed (my lastReadAt), scoping the effect to the caller's own read state, and notes the login requirement. It stops short of explaining any impact on unread counts or what the response returns.

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?

Two short clauses, with the auth prerequisite and the action both front-loaded and no padding. The '登录;' prefix is slightly telegraphic but not wasteful.

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 single-parameter, non-destructive, idempotent toggle with no output schema and full schema coverage, this is close to complete: the effect is named and auth is flagged. Only the absence of any comparison to sibling read-marking tools keeps it from a 5.

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 coverage is 100% and the single parameter (conversationId, '会话 id') is fully documented in the schema. The description does not add any meaning to the parameter beyond what the schema already states, so the baseline of 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?

The description gives a specific verb+resource ('mark a conversation as read') and even names the underlying field change ('updates my lastReadAt'), which separates it from read-only siblings like get_conversation or read_messages. It does not explicitly disambiguate against the closely-named sibling mark_organization_notification_read, so it falls short of a 5.

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 leading '登录' (login) indicates an authentication prerequisite, which is useful context. However, there is no guidance on when to use this versus read_messages, get_conversation, or mark_organization_notification_read, and no stated exclusions, so usage is only implied.

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