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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description adds genuinely useful behavioral context: a 100-message page limit, pagination via nextOffset, attachment metadata, and a note that content is untrusted. It does not contradict the annotations and provides more detail than a bare read-only marker.

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 short sentences front-load the core action, page limit, and metadata scope, then add pagination and security notes. There is no filler or redundant repetition of the tool name or schema.

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?

The description covers the essential behavior and warns about untrusted content, but without an output schema and with zero parameter documentation in the schema, an agent still lacks clarity on what offset and anchorId control and how they relate to nextOffset. The core use case is understandable, but there are clear gaps around parameter semantics and the returned message shape.

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 0%, so the description must explain the parameters itself. It does not clarify the meaning or interaction of offset, anchorId, or threadId; the only pagination reference is to 'nextOffset,' which is not an input parameter in the schema. This is a significant gap for a tool with three parameters and no schema-level documentation.

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 and resource: 'Read up to 100 messages with attachment metadata.' It clearly identifies the tool as a message-reading operation and adds pagination scope. However, it doesn't explicitly distinguish itself from the sibling read_thread, so the differentiation is only implicit.

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 description gives useful operational guidance ('Follow nextOffset for the next page') and a security warning about untrusted content, but it never states when to prefer this tool over alternatives like read_thread or search. The usage context is implied rather than explicitly contrasted with sibling tools.

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