get_message

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

Discloses the untruncated message length limit (~20k chars), which is important behavioral context. However, no annotations are provided, and the description does not cover authentication requirements, response format, or error conditions, leaving gaps.

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 that are front-loaded with key context (multi-account) and functionality. No wasted words, though the structure could be slightly improved by integrating the two ideas.

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?

Lacks explanation of the return value structure (e.g., fields like body, headers) and does not mention that message might be part of a thread. Given the absence of an output schema, the description should provide more details on what 'in full' entails.

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 'account' parameter is described in both schema and description, but 'messageId' lacks description in both places. With 50% schema coverage, the description adds some context for account but does not fully compensate for the missing messageId explanation.

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?

Clearly states 'Read a single email message in full' with a specific verb and resource, and distinguishes from sibling tools like get_thread and search_threads by focusing on a single message. Provides additional context about multi-account support.

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?

Implies usage for reading a full message, and mentions multi-account, but does not explicitly specify when to use this tool versus alternatives (e.g., get_thread for thread context). No 'when not to use' guidance is provided.

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