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

With no annotations, the description must carry the transparency burden. It discloses the credential dependency (IMAP configured in .env) but doesn't explain what 'status information' includes, whether the call is read-only, makes network requests, or what response to expect. This leaves significant behavioral ambiguity.

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 sentences, front-loaded with the primary action and followed by a credential/account tip. Every word earns its place with no redundant content.

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?

Without an output schema, the description should explain what status data is returned, but it remains silent. The nested imap_config object and optional parameters are only partially contextualized, leaving the tool under-specified for an agent to predict its behavior and output.

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 already covers account and mailbox details, and the description adds the nuance that credentials are unnecessary if IMAP is pre-configured in .env, which clarifies the role of imap_config. However, it doesn't elaborate on mailbox options or the imap_config object beyond the schema, so the added value is modest.

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-resource pair ('Get status information for an email mailbox') that clearly distinguishes it from siblings like read_inbox or list_mailboxes by focusing on 'status'. However, it doesn't explicitly differentiate from other status tools (e.g., get_health_status) and 'status information' is somewhat vague.

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 provides clear context on credential handling: if IMAP is configured in .env, no credentials are needed, and it instructs to use the 'account' parameter to select a named account. It doesn't explicitly mention when to use this over alternatives, but the situational guidance is direct.

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