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

The statement 'marks the lead's messages as read' is genuinely valuable behavioral disclosure (a state-changing read receipt), but it conflicts with the declared readOnlyHint=true. Beyond that one clause, nothing is said about the response shape, pagination, or history depth.

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-clause pair; the ordering guarantee ('oldest first') and the side effect are both front-loaded with no filler. Nothing extraneous, though it is terse to the point of omitting routing guidance.

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 one-parameter read with no output schema, the description covers ordering and side effects, which is the essential part. It leaves the agent guessing about the return contents (sender attribution, timestamps, attachments) and whether there is any limit on how much history is returned.

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?

There is a single required parameter and the schema already documents it fully ('Id from list_leads'), so the baseline is 3. The description adds no further meaning about leadId, but none is needed.

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 the resource precisely: 'the conversation with a lead', which distinguishes it from the student-oriented read_chat and list_conversations siblings. It reads as a retrieval, though no explicit verb is used, so it lands just short of a full verb+resource statement.

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 (open a lead's conversation to read messages), but the description never says when to prefer this over read_chat or list_conversations, nor any prerequisite such as having a leadId from list_leads. The analogy 'like opening it in the app' gestures at intent without giving selection criteria.

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