read_email

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

With no annotations, the description must disclose behavioral traits, but it only states the action. It does not clarify whether emails are marked as read, how 'latest' is determined, what happens if fewer than 5 unread emails exist, or any authentication requirements. The read-only nature is implied but not explicit.

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 concise sentence with no wasted words, which is efficient. However, it omits critical information such as the parameter meaning and behavioral nuances, so its brevity comes at the expense of utility.

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 tool with one required parameter, no output schema, and no annotations, the description is severely incomplete. It fails to explain the parameter, the return format, edge cases, or any side effects, leaving the agent unable to call it correctly.

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 sole parameter 'name' is required but has no schema description (0% coverage) and is entirely absent from the tool description. The agent has no basis to infer what 'name' refers to—whether it is an account, folder, or other identifier—making correct invocation impossible.

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 a clear action ('Read') and a specific resource ('latest 5 unread emails'), which distinguishes it from search, send, and configuration tools. However, it does not explicitly differentiate it from get_all_emails or get_emails_by_date, which could also return emails, so it lacks a definitive exclusion.

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 is provided on when to use this tool versus siblings like search_emails or get_all_emails. There is no mention of context, prerequisites, or alternatives, leaving the agent to guess the appropriate scenario.

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