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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description adds ordering (oldest first), an auth requirement ('requires read scope'), and the shape of the returned content blocks. The only omission is whether results are paginated or capped, which matters for long chat histories.

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 short sentences with zero filler: the core action and ordering come first, followed by the payload shape and the access requirement. Every clause carries information an agent would otherwise have to guess.

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 tool with no output schema, the description covers action, ordering, return structure, and auth, which is nearly everything needed to call it correctly. Absent pagination/limit behavior is the one remaining gap.

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 parameter, chat_id, already documented at 100% schema coverage as a UUID 'chat session ID'. The description adds no further meaning about how to obtain or scope that ID, so the schema carries the burden and the baseline of 3 applies.

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 ('list the messages in a chat session') plus the ordering guarantee 'oldest first', so an agent knows exactly what it retrieves. It does not differentiate itself from plausible siblings such as get_conversation_messages or list_pending_messages, leaving that distinction to be inferred.

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 by the resource name: call it when you need the message history of a known chat session. There is no explicit when-to-use vs when-not statement, no mention of alternatives for cross-chat or pending-message queries, and no prerequisites beyond the scope note.

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