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

With no annotations provided, the description must fully communicate behavioral traits. It mentions that the tool returns 'full message content' and 'extracted verification links/codes', suggesting parsing. However, it fails to disclose whether the operation is read-only, if authentication is required, rate limit implications, or any side effects. This lack of transparency is a significant gap for a tool that retrieves content.

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 a single, front-loaded sentence that conveys the core purpose without extraneous words. However, it could be improved by adding parameter details without losing conciseness. It earns its place but is slightly under-informative given the tool's complexity.

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 absence of annotations and output schema, the description is incomplete. It does not mention return format, error conditions, or relationship to sibling tools beyond implicit differentiation. The tool is straightforward, but the description leaves significant gaps in operational context, especially regarding parameter semantics and behavioral expectations.

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%, and the description does not explain any of the three parameters (mailboxId, messageId, includeRaw). The description only hints at the output content but adds no meaning to the input schema. The agent receives no guidance on what values are valid, the role of includeRaw, or the format of IDs, which is critically insufficient.

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 clearly states the verb 'Get' and the resource 'full message content', and specifies the extraction of verification links/codes, which differentiates it from sibling tools like agent_tempmail_list (which likely retrieves metadata) and agent_tempmail_wait (which waits for messages). This makes the tool's purpose highly specific and unambiguous.

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 provides no guidance on when to use this tool versus alternatives, such as when to choose get over list or wait. It does not mention prerequisites, use cases, or conditions for using optional parameters like includeRaw, leaving the agent to infer usage without context.

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