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

No annotations are provided, so the description carries the full burden; it discloses the analytical payload (sentiment, summary, topics, compliance flags, suggested action), which is genuinely useful. It does not state read-only semantics explicitly, cost/latency implications of running AI analysis on every call, or what happens if the message_id is unknown or belongs to another firm.

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?

A single dense sentence with the resource and the value proposition front-loaded and no filler. It is appropriately sized for a two-parameter read tool, though the enumerated field list is the only content it offers.

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?

An output schema exists, so return shape need not be described, and the description's field list is a helpful preview. However, for a tool with an undocumented firm_id parameter, no annotations, and AI-derived fields that may have accuracy or compliance implications, key operational context 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% for two parameters, and the description supplies nothing about either. message_id's role is guessable from the name, but firm_id has a default of empty string and no explanation of whether it is a tenant scope, an optional override, or required for access control — a real ambiguity the description should resolve.

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?

Specific verb (Get) plus resource (full email) and an enumeration of the returned analysis fields. It implicitly contrasts with the sibling list tool get_email_messages via 'full email,' but never names it, so differentiation is inferred rather than stated.

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 is only implied: the word 'full' suggests fetching a single detailed record rather than a list, but the description never says 'use this after get_email_messages' or states any precondition. An agent must infer the retrieval-vs-listing split from sibling names alone.

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