get_email

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

With no annotations, the description should disclose side effects, auth requirements, or limitations. It only says 'Fetch' which implies read-only, but doesn't mention any behavioral details like rate limits, error cases, or what happens if emailId is invalid. Extremely sparse.

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 sentence with no fluff, which is concise. However, it is under-specified to the point of being unhelpful, so while it's not verbose, it's not appropriately sized given the tool's complexity (2 parameters, no annotations).

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?

The description fails to provide essential context: what the thread contains, how inboundLimit works, what the returned data looks like, or any caveats. Given the lack of annotations and output schema, this is severely incomplete.

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 0%, so the description must explain parameters. It mentions 'one mailbox address' but does not explicitly map that to emailId, and inboundLimit is completely unexplained. No additional meaning is provided.

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 identifies the action (fetch) and the resource (message thread) and specifies the scope (one mailbox address). It is specific enough to differentiate from list_emails (which lists emails) and select_email (which selects an email), though the exact meaning of 'mailbox address' vs the emailId parameter could be clearer.

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?

No guidance on when to use this tool versus alternatives like list_emails or select_email. The description doesn't mention when a thread fetch is appropriate or any exclusions or prerequisites.

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