stalwart_search_emails

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

No annotations are provided, so the description carries full burden. It mentions impersonation capability but fails to disclose read-only nature, pagination behavior beyond limit, or required permissions. This is a significant gap for a search tool without annotation coverage.

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?

Two-sentence overview plus a compact Args list. Every line adds value and is front-loaded with the tool's purpose, making it highly efficient.

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?

With an output schema present, return values need not be explained. The description covers all parameters and override behavior. It lacks contextual notes about when to use vs siblings, but that is more of a guidelines issue; the invocation semantics are complete.

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?

Description provides concrete meaning for all five parameters: account_id special value 'b', mailbox_role allowed values, mailbox_id override, text search scope, and limit default. This fully compensates for the 0% schema description coverage.

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 'Search emails in an account' with a specific verb and resource. It distinguishes from siblings like get_email (single retrieval) and list_mailboxes (folder listing).

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 explicit when-to-use or alternatives are given. The parameter descriptions imply usage for searching, but no exclusions or references to sibling tools like get_email are provided, leaving the agent to infer appropriate use.

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