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

With no annotations provided, the description carries the full burden and does meaningful work: it discloses that HTML is converted to plain text, that attachments are represented by metadata fields including attachmentId, and that the operation is a read. It does not cover error behavior or truncation details, but core behavioral traits are transparent.

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?

The description is three compact sentences with the core action front-loaded, followed by useful behavioral detail and ID routing. Every sentence earns its place and there is no filler.

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 no output schema and no annotations, the description covers the essential outcomes: full body, attachment metadata, HTML conversion, and how to obtain messageId. Minor gaps such as exact response envelope or error cases remain, but the description is sufficient for an agent to invoke the tool correctly in most situations.

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?

The schema already describes mailbox and maxChars, while messageId has no schema description. The description compensates by telling the agent to obtain messageId from search_outlook_messages or list_messages, and it clarifies how attachmentId returned by this tool is used downstream, adding meaning beyond the schema.

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', and a specific resource, 'one message in full', and clearly enumerates what that includes: body text and attachment metadata. It also distinguishes itself by naming the downstream attachment tools and the ID sources, making its role distinct among large sibling lists.

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?

It explicitly tells the agent where to get the messageId and explains that the attachmentId is consumed by read_outlook_attachment and save_outlook_attachment_to_onedrive, giving clear routing to sibling tools. It lacks an explicit 'when not to use this' exclusion, but the context is clear enough for an agent to select it appropriately.

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