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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior beyond that: reading does not clear unread state, and only mark_conversation_read does. It does not discuss truncation/pagination limits when `limit` cuts off results.

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?

Three tight sentences with no filler; the core action comes first, the unread-state caveat second, and the pagination tip last. Every sentence carries information an agent needs.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. The description covers the non-obvious unread semantics and the cursor pattern. A minor gap remains around how 'oldest first' interacts with the schema's 'default 100, newest' limit 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 coverage is 100%, so the baseline is 3, but the description adds real semantic value for `after` — clarifying it should be the created_at of the last message already seen, i.e. a cursor rather than an arbitrary filter. `limit` is left to the schema, which is acceptable given full coverage.

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?

States a specific verb and resource ('read the messages between the user and one other TraydStar member') plus the ordering ('oldest first'), which is enough to separate it from list_conversations (many conversations) and send_message (writes). No ambiguity about what is returned.

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?

Gives concrete usage direction for incremental fetching ('Pass `after` ... to get only newer messages') and implicitly routes the agent to mark_conversation_read for the read-state change. It stops short of explicitly stating when not to use it or naming sibling alternatives like list_conversations.

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