get_unread_emails

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

With no annotations provided, the description bears the full burden of behavioral disclosure, but it fails to mention any behavioral traits such as authentication requirements, rate limits, or what happens when no unread emails exist. The output schema exists but the description does not leverage it to clarify return behavior.

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 containing no extraneous words. It is concise and immediately communicates the core purpose.

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 tool has zero parameters and an output schema likely describing the return format, the description is minimally adequate but lacks important context such as whether it returns all unread emails or a subset, and whether pagination is involved. The description could be more complete, e.g., mentioning the scope or ordering.

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 tool has zero parameters, and the input schema coverage is 100% (empty). Baseline for zero parameters is 4, and the description adds no additional parameter details. It is adequate given the lack of parameters.

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 'Get a list of unread emails' uses a specific verb 'Get' and clearly identifies the resource 'unread emails', leaving no ambiguity about the tool's function. It is distinct from the sibling tool 'create_draft_reply', which is a write operation.

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 usage guidelines are provided. The description does not state when to use this tool versus alternatives, nor does it offer any context about prerequisites or contraindications. The sibling tool 'create_draft_reply' is mentioned in context but not in the description itself.

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