email_list_accounts

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

No annotations are provided, so the description bears the burden of behavioral disclosure. It states the tool lists accounts and reports connection status, which implies a read-only operation. However, it doesn't disclose any side effects (though none seem likely), limitations, or what happens with unconfigured/duplicate accounts.

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?

A single sentence that fully states what the tool does with zero wasted words. Efficiently front-loads the purpose.

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 zero-parameter, read-only listing tool, this is mostly sufficient. The description tells the agent what it will get. However, without an output schema, the agent doesn't know the exact return shape (field names, structure), and the description doesn't hint at it beyond 'accounts and connection status'. Given the simplicity, this is adequate but not exhaustive.

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 tool has 0 parameters, so there is nothing for the schema to cover beyond an empty object. The description adds value by clarifying what will be returned (accounts + connection status). With no parameters, there's nothing more needed here.

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?

Clear verb+resource: lists configured email accounts and shows connection status. Distinguishes from siblings like email_add_account (add) and email_remove_account (remove). It could be more specific about what 'connection status' entails, but the purpose is clear.

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?

No guidance on when to use this tool vs alternatives. Given many sibling tools, it would help to note this is a read-only overview tool useful before account operations, but the description offers no context about use cases or when to prefer it over email_test_account or mail_sync_status.

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