List Mailbox Imports

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

Annotations already provide readOnlyHint and openWorldHint. Description adds that it lists 'recent' imports with 'status and counters', which adds some context but doesn't specify what 'recent' means or if there is pagination. Adequate but not rich.

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?

Single sentence with no fluff. Key information is front-loaded and every part adds value.

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's simplicity, annotations, and existence of an output schema, the description is fairly complete. It covers what is listed (imports) and what is returned (status and counters). The 'recent' qualifier is noted. It doesn't mention pagination or sorting, but for a straightforward list tool it's sufficient.

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 description 'ShipMail resource ID.' for the single required parameter. Description does not add further parameter semantics, so baseline score of 3 is appropriate.

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?

Description clearly states verb (list), resource (recent imports for a mailbox), and what is returned (status and counters). It distinguishes from sibling tools like shipmail_get_mailbox_import (singular) and shipmail_create_mailbox_import.

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?

Usage is implied (listing recent imports for a mailbox), but no explicit guidance on when to use this tool vs shipmail_get_mailbox_import for a specific import or other list tools. Not misleading but lacks exclusions or alternatives.

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