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

No annotations are present, so the description must carry the behavioral burden. The verb 'List' implies a non-mutating read operation, and the 'one mailbox' scope is explicit, but the description does not mention output behavior, permission requirements, or whether hidden/system rules are included.

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 a single focused sentence with no filler. Every phrase, including 'inbox rules', 'auto-file incoming mail', and 'one mailbox', contributes to agent understanding.

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 one-parameter list tool, this reaches the minimum viable level: the purpose, object, and required mailbox are all identifiable. However, because there is no output schema or annotations, and because usage versus alternatives is not addressed, the agent gets an adequate but not fully complete picture.

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 fully documents the sole mailbox parameter and enriches it by identifying it as a connected Outlook/Microsoft 365 mailbox and directing the caller to list_authorized_mailboxes for valid options. This adds meaningful context beyond the raw parameter name and type.

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 'List' as a specific verb, identifies the resource 'inbox rules', and narrows the scope with 'auto-file incoming mail' and 'one mailbox'. This clearly distinguishes the tool from rule creation/deletion and from listing mail folders or messages.

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?

There is no guidance about when to select this tool over alternatives such as create_inbox_rule, delete_inbox_rule, or list_mail_folders. The only usage hint, 'Call list_authorized_mailboxes', appears in the parameter schema and supports parameter selection rather than tool selection.

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