Create Custom SimpleLogin Alias

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

Annotations already indicate a write operation (not read-only, not destructive, not idempotent). The description adds the dependency on the alias-options endpoint, but does not disclose other behavioral traits like rate limits, auth requirements, or side effects.

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?

A single sentence that efficiently conveys the tool's purpose and a critical prerequisite. The parenthetical about the UI picker is minor but does not detract from conciseness.

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 existing output schema, the description does not need to explain return values. It covers the essential prerequisite (signed suffix) and purpose. Missing details about alias prefix constraints or success/error messages, but these are not required given the output schema and annotations.

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 description adds context for two key parameters (aliasPrefix and signedSuffix) by relating the suffix to the alias-options endpoint. For the other four parameters, it provides no additional meaning beyond the input schema, which already has descriptions for most but not all (note and hostname lack descriptions).

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 creates a custom SimpleLogin alias with a user-chosen prefix and signed suffix. It distinguishes from sibling tool alias_create_random by emphasizing the custom prefix choice.

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?

It specifies a prerequisite (obtaining signed suffix from alias-options endpoint) and hints that the UI picker normally handles this. However, it does not explicitly advise against using this tool for random alias creation, which is handled by a sibling.

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