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

Annotations only cover readOnlyHint=true; the description adds two behaviors beyond that: results are ordered oldest-first and ownership is verified before anything is returned. The authorization check is genuinely useful context an agent cannot get from the annotations. It does not discuss pagination or absence handling.

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, front-loaded with the core action and ordering, followed by an input-provenance note. No filler, though the ownership sentence is somewhat detached from the main statement.

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 single-parameter read tool with an output schema, the description covers the action, ordering, input source and an authorization behavior. Return-format details are correctly omitted since an output schema exists. Only usage routing against siblings is missing.

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 burden falls on the description, and it does compensate by explaining that `conversation_id` is the ID found in related_conversations entries. That is real provenance guidance, though format/validation details remain unspecified.

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 (fetch), resource (all messages in one conversation) and ordering semantics (oldest first). It does not, however, distinguish itself from nearby siblings like recent_messages or search_semantic, so an agent must infer the boundary.

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 context is implied by the provenance note that `conversation_id` comes from related_conversations entries, which tells the agent where to get the input. There is no explicit when-to-use/when-not statement or named alternative against recent_messages or search tools.

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