receive_email

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

Goes well beyond the annotations by disclosing a real side effect (POP3 semantics delete the mail server-side) and a critical operational caveat (the app's inbox is not exposed, so the caller must persist the return value). It also implies the call blocks up to a timeout on an empty mailbox, consistent with the schema's timeout_secs. This is exactly the extra context annotations cannot carry.

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?

Three tight sentences: the action first, then the protocol/side-effect, then the retention warning. No filler, and the most important caveat is front-loaded rather than buried.

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 the description need not explain the return shape, and it correctly spends its budget on prerequisites, side effects, and the retention requirement instead. Nothing needed to invoke it safely is missing.

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 100% and both parameters are already well documented there, including defaults and the empty-mailbox timeout behavior. The description adds no parameter-level semantics (e.g., device naming conventions), so the baseline 3 applies.

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 concrete verb+resource (download the account's new mail over POP3) and names the mechanism, which cleanly separates it from send_email and configure_email in the sibling list. An agent can tell exactly what the call produces: the inbox contents for one device.

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?

It frames the tool as the 'Press Receive' action and ties it to a device that has already been set up via configure_email (echoed in the schema). It gives no explicit when-not-to-use or explicit alternative for reading existing mail, so it stops short of 5.

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