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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered structurally. The description adds a genuine behavioral detail the annotations do not — results are ordered oldest-first by first-read time — but says nothing about pagination, result limits, or empty-result behavior for a list endpoint.

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?

One compact sentence front-loads the returned information, with the raw HTTP path appended as a secondary detail. Nothing is wasted, though the endpoint string is arguably redundant for an MCP agent and slightly dilutes the otherwise tight phrasing.

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?

There is no output schema, so the description must describe return values; it partially does so (reader identity plus first-read timestamp, ordered oldest first). It omits pagination/limit behavior and the shape of each receipt entry, leaving real gaps for a list endpoint, though the single well-documented parameter and rich annotations keep the tool usable.

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 parameter includes a concrete example value ('ti_0D4QABCC06000'), so the schema fully carries parameter meaning. The description adds no additional parameter semantics, which is acceptable here but earns only the 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 the specific resource (read receipts for one conversation item) and the exact payload semantics ('who has read ... and when they first read it'), which cleanly separates it from siblings like get_conversation_item or list_conversation_items. The verb 'list' is only carried by the name/title, not the description body, but the resource and scope are unambiguous.

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?

Usage is implied: an agent can infer you call this when you need read status for a single item. However, there is no explicit when-to-use statement, no prerequisite (e.g. needing a conversation item id obtained elsewhere), and no mention of alternatives such as get_conversation_item which returns the item itself.

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