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

With no annotations, the description carries the behavioral burden. It discloses the read-only nature ('Read'), the ordering, and that bodies are included. However, it does not mention potential limitations such as message size, truncation, or whether the operation marks messages as read. For a read tool, the core behavior is transparent, but a note on large conversation handling would be beneficial.

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 with zero redundancy. The main function is front-loaded, followed by usage guidance and a prerequisite. Every sentence earns its place, and the description is appropriately sized for the tool's simplicity.

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?

Given the lack of an output schema, the description does not describe the return format (e.g., structure of messages, fields, pagination). It also omits any caveats about performance or size for large conversations. While the core purpose is clear, an agent might need more detail on what the response contains. This is a moderate gap for a tool that reads multiple messages.

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 coverage is 67% (mailbox and maxCharsPerMessage have descriptions; conversationId does not). The description compensates for the undocumented conversationId by explicitly stating 'Get the conversationId from search_outlook_messages', adding practical meaning. It also implies the purpose of maxCharsPerMessage through context (body budget), though the schema already covers that. This adds value beyond the schema for the key parameter.

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'), a specific resource ('every message in a conversation'), and adds ordering ('oldest first') and content ('with bodies'). It explicitly distinguishes itself from get_outlook_message and references search_outlook_messages, making the tool's purpose unambiguous and distinct from siblings.

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 clear usage guidance: use this instead of repeated get_outlook_message calls when the whole exchange is needed. It also tells the agent where to obtain the conversationId (from search_outlook_messages), providing a prerequisite and alternative. No ambiguity remains about when to choose this tool.

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