stalwart_list_accounts

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

With no annotations provided, the description carries the full burden for behavioral transparency. It explains that the list returns a 'compact summary' but does not disclose side effects, authentication requirements, pagination behavior, or sorting/ordering. The read-only nature is implied but not made explicit.

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 appropriately concise, with a clear purpose statement and a structured Args section. Every sentence adds value, and the parameter explanations are efficient and readable.

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 and the presence of an output schema, the description is mostly complete. It covers purpose and parameter semantics, but lacks explicit guidance on use cases or interactions with other account-related tools, which is a minor gap for a list operation in a larger toolset.

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 description coverage is 0%, but the description fully compensates by explaining both parameters: 'limit: max rows (default 50)' and 'search: optional substring match on account name'. This adds meaningful semantics beyond the raw schema types and defaults.

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 clearly states the tool 'List mail accounts (users) with a compact summary', using a specific verb and resource. It differentiates from sibling list tools like list_domains or list_mailboxes by focusing on accounts, though it does not explicitly contrast with stalwart_list_principals which may also cover accounts.

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 is provided on when to use this tool versus alternatives, such as when to prefer get_account for details or list_principals for broader principal listing. The description only explains the parameters, not the intended context or exclusions.

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