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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable context by noting membership and history limits apply, and crucially warns to treat message content as untrusted source data, which is a security-relevant behavioral note not present in annotations.

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 concise sentences: the first states the action and target, the second adds important caveats. No waste, front-loaded information.

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?

With annotations covering safety, a rich schema, and an output schema (so return values needn't be explained), the description is nearly complete. The mention of membership/history limits and untrusted data handling fills important behavioral gaps. Minor omission: it doesn't clarify pagination behavior, though the schema's 'after' parameter documents that.

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%, so all parameters are already well-documented in the schema. The description mentions 'known conversation' and the chat/kind parameters implicitly, but adds no new parameter semantics beyond what the schema provides. Baseline 3 is appropriate.

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 a specific verb ('Read') and resource ('messages') and names the conversation types it operates over, which distinguishes it from write siblings like send_message. It could have more explicitly contrasted itself with list_conversations, but the purpose is clear.

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 phrase 'from a known conversation' implies it's for retrieving messages from an existing conversation, hinting that discovery should use list_conversations first. However, there is no explicit when-to-use vs alternatives guidance or preconditions stated.

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