Get Email

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

No annotations are provided, so the description must convey behavioral traits. The verb 'Retrieve' implies a read-only operation, and the note about search_emails returning 'the same full data' hints that get_email returns full email data. However, it does not explicitly state safety, error behavior, or any special side effects, leaving moderate gaps for a no-annotation tool.

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 sentences, front-loaded with the purpose, followed by usage guidance and a note about an alternative. Every sentence adds value and there is no unnecessary verbosity.

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?

For a simple getter with one parameter and no output schema, the description is fully sufficient. It states both what the tool does and when to use it, and the note about search_emails clarifies the return data, covering the main context an agent needs.

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 has 100% coverage with a clear description of email_id ('The EmailId to retrieve'), and the parameter name is self-explanatory. The description reinforces the use of the ID but does not add extra semantic detail beyond what the schema provides.

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 the exact action: 'Retrieve a single logged email by ID.' This clearly distinguishes it from sibling tools like search_emails and get_emails_attached_to_contact by specifying a single record and the use of an ID.

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?

Explicitly states when to use: 'Use this when you already have an EmailId and need the record.' It also provides an exclusion: 'Only use get_email when you have an ID but not the data,' and names the alternative search_emails with a note about it returning the same full data.

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