mailkite_list_app_passwords

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

The readOnlyHint annotation already covers safety, and the description adds value beyond it by explaining what an app password is (accesses mail over IMAP and the mailbox API) and its scope (domain and address pattern). No behavioral surprises disclosed or needed for such a simple read-only listing.

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 compact sentences, front-loaded with the action, and all additional context earns its place: what an app password is, its scope, and the auth requirement.

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 list tool, the description is complete: it identifies what is listed, what the items mean, their scope, and the token requirement. Minor gap is no mention of output shape or pagination, but the absence of params and presence of readOnlyHint make this a small concern.

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 takes zero parameters, so there is nothing to document; the baseline of 4 applies. The description adds resource context (which app passwords are listed) beyond the schema.

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 states a specific verb ('List'), a clear resource ('the account's app passwords'), and explains what these passwords are for ('opens a mailbox over IMAP and/or the mailbox API, scoped to a domain and an address pattern'). This goes beyond the bare name and distinguishes it from other list_* siblings.

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 clear context that this operates on the account's app passwords and explains what app passwords doable. The auth prerequisite ('Requires a management session token') is a useful usage condition. It does not name alternatives explicitly, but as a standalone list operation the context is clear.

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