Add a mail account

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

Describes security behavior: password stored in Keychain, not registry/logs, and warns that password passes through context/logs. This adds value beyond the openWorldHint annotation. Some details on verification behavior are missing.

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 focused sentences plus a security note. Efficiently front-loaded with main action. Could be slightly more structured, but no waste.

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?

No output schema, and description does not explain return value or error behavior. It lacks details on what 'verify' entails or failure handling. Adequate but incomplete.

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 coverage is high (91%), but description adds context: provider defaults, port defaults, STARTTLS. It explains the purpose of parameters beyond the schema, like security context for appPassword.

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 'Add and verify a mail account' with a specific verb and resource. It distinguishes from sibling tools by focusing on account creation, unlike message management or label tools.

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?

Provides explicit guidance on providers, default ports, and when to use GUI for privacy. It also explains required parameters for 'imap' provider, giving clear context and alternatives.

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