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

Annotations already declare the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds genuine behavioral context beyond annotations: messages come back oldest-first and include bodies. It stops short of explaining truncation behavior or how maxCharsPerMessage affects results.

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 tight sentences with the core action and ordering front-loaded, and no filler. The alternative-tool and prerequisite guidance each earn their place.

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?

No output schema exists, and the description covers ordering, body inclusion, the alternative to avoid, and the conversationId source. Minor remaining gap is explicit truncation/pagination behavior, though the maxCharsPerMessage default in the schema implies per-message budgeting.

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 are documented in the schema, but conversationId has no schema description. The description compensates by explaining where to obtain the conversationId (search_outlook_messages), adding meaning the schema lacks.

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 (read) and resource (Outlook conversation), and specifies the scope: every message in the conversation, oldest first, with bodies. It also explicitly distinguishes itself from the sibling get_outlook_message, so an agent can select between them without opening schemas.

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?

Directly states when to use it ('when you need the whole exchange') and names the alternative it replaces ('repeated get_outlook_message calls'). It also gives the prerequisite for obtaining the required conversationId from search_outlook_messages.

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