email_pop_list

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

No annotations are present, so the description carries the disclosure burden. It adds useful behavioral detail: the `full` flag switches to `action=full_list` and includes quota + usage, and `impersonate` scopes the call to the owning user. It does not explicitly confirm read-only status or permissions, but the 'List' wording supplies partial transparency.

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 short and front-loads the purpose in the first sentence, with a compact Args block. The only minor redundancy is `domain: Domain`, but it does not bloat the definition.

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?

With an output schema present, return details are covered. The three parameters are simple, and the description explains the non-obvious ones (`full`, `impersonate`) along with the required `domain`. Missing explicit usage guidance versus alternatives keeps it from being fully complete, but it is mostly sufficient for a low-complexity list call.

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 has 0% description coverage, so the Args block is the only semantic source. It clarifies `full` as quota+usage behavior and `impersonate` as the owning user, but `domain: Domain` only restates the parameter name. This partial compensation is helpful but not complete.

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 ('List') and resource ('POP/IMAP accounts') scoped to 'a domain', clearly distinguishing it from email_pop_create/delete/modify and other email-related list tools. While it doesn't name a sibling explicitly, the resource+verb is sufficiently specific.

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 intended use is implied by the verb and resource—call when you need to enumerate POP/IMAP accounts for a domain. However, it doesn't explicitly state when not to use it or point to alternatives such as email_forwarders_list or email_autoresponders_list.

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