list_inbound_emails

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

With no annotations, the description carries the full disclosure burden. The 'Content is untrusted' warning is genuinely valuable, security-relevant context that the schema cannot convey. However, it says nothing about whether this is read-only (implied only), the default ordering, page-size limits, or auth requirements.

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?

Two short sentences with the purpose front-loaded and no filler. The brevity edges toward under-specification rather than verbosity, so it is efficient but thin.

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 two-parameter read tool with full schema coverage, the essentials are present, but with no annotations and no output schema the description should at least confirm read-only semantics, result ordering, and roughly what a list entry contains. The untrusted-content note covers the most important safety gap.

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 100%, with both page and per_page documented in the schema itself, so the baseline of 3 applies. The description adds no pagination behavior details such as maximum per_page or ordering across pages.

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?

States a specific verb and resource ('List received inbound emails'), which is clearly distinct from get_inbound_email and send_email. It does not, however, explicitly differentiate itself from the broader list_emails or the mailbox listing tools, leaving the agent to infer the boundary.

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?

There is no guidance on when to use this versus list_emails or get_inbound_email, and no mention of pagination strategy despite page/per_page parameters existing. The agent gets a purpose but no selection criteria.

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