Update SimpleLogin Alias

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

Annotations indicate idempotentHint=true, and the description confirms 'update in place' and 'replaces the current set' for mailboxIds, adding behavioral context beyond the structured fields. It does not contradict annotations and clarifies partial update behavior.

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?

Three well-structured sentences: purpose, usage hint, and ID sourcing context. No superfluous information; each sentence serves a distinct 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?

The description covers how to find required IDs, partial update semantics, and the replacing behavior for mailboxIds. With an output schema present, it need not detail return values. Minor omission: does not mention error handling or state that 'name' can be cleared via empty string (though schema covers it).

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 86%, and the description adds meaning by explaining the required aliasId must come from alias_list and how mailboxIds relate to a separate workflow. It also emphasizes partial updates, which is not fully captured by the schema alone.

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 'Update an existing SimpleLogin alias in place' and lists exactly which attributes can be modified (display name, note, mailboxes, PGP on/off, pinned state). This specific verb+resource combination distinguishes it from sibling tools like alias_create_*, alias_delete, and alias_toggle.

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?

The description advises 'Provide only the fields you want to change; at least one is required' and directs users to alias_list to find aliasId and to an equivalent mailbox-list workflow for mailbox_ids. It provides clear context on prerequisites but does not explicitly state when NOT to use the tool or list alternative tools for different scenarios.

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