List mailboxes

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

The description discloses key behavioral details: it returns a paginated list (max 25 per page), supports an optional search query, and includes specific fields like address, name, flags, password strength, and timestamps. This is valuable context beyond a bare 'list' statement, and since no annotations are present, the description carries the full burden effectively.

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 two sentences, front-loads the main purpose, and includes essential details without fluff. Every word earns its place.

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 list operation, the description covers the primary aspects: scope (all domains), pagination behavior, search capability, and return fields. It lacks detail on default page size or error handling, but these are minor for a read-only list tool.

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 input schema already provides descriptions for all three parameters (page, query, paging), so the description adds little new semantic detail. It mentions pagination and search generically, but does not clarify the interaction between page and paging or search syntax, which would be valuable.

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 specifically states 'List all mailboxes in the account across every domain' with a clear verb and resource, and distinguishes from sibling tools like get_mailbox by emphasizing the collection scope. It also notes pagination and search, making the tool's function unambiguous.

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 description provides clear context that this tool is for retrieving a list of all mailboxes, which implies it should be used for bulk listing rather than fetching a single mailbox (get_mailbox). It does not explicitly name alternatives or exclusions, but the scope is evident from the text.

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