get_emails

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds batch-size limits and the notion of 'ordered partial results,' but this behavior is cryptic and not explained in terms of what causes partial results or how ordering is determined.

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 with no filler. However, 'ordered partial results' is dense and could be clearer, so it loses a point for being overly terse.

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 output schema and annotations cover return-value shape and safety, so the description does not need to repeat those. Still, for a batch read tool, an agent would benefit from more explicit guidance about when to call it versus siblings and what 'identities' refers to.

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%, so the description should compensate by explaining the identities structure or max_text_chars. It only weakly hints at '1-10 exact identities' and provides no guidance on max_text_chars or the meaning of the required identity fields.

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 uses a specific verb ('Read') and resource ('plain text for 1-10 exact identities'), which makes clear this is a batch plain-text retrieval tool. It is distinguishable from the single-item get_email and HTML-focused get_email_html siblings, though 'identities' is not explicitly defined.

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 phrase '1-10 exact identities' implies a batch use case and hints at a limit, and 'plain text' distinguishes this from HTML retrieval. However, the description never explicitly states when to prefer this tool over get_email or search_emails, nor does it state exclusions.

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