Create SimpleLogin Alias Contact

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

The description discloses that the tool is idempotent ('or fetch, if it already exists'), aligning with the idempotentHint annotation. It also mentions the return value (reverse_alias_address). No contradictions with annotations.

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?

The description is concise with two sentences, no redundant information, and front-loads the key action and 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 is complete for a tool with an output schema, explaining the return value and usage. It could mention the parameter order or dependencies, but overall sufficient.

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 value by clarifying the format of the 'contact' parameter. However, with 67% schema description coverage, the description does not cover 'aliasId' or 'account_id' beyond what the schema provides, meeting the baseline.

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 or fetches a reverse-alias contact, specifying the use case of sending FROM an alias TO an external address. It distinguishes from sibling tools like alias_create_custom which create aliases, not contacts.

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 explains when to use the tool (to send from an alias to an external address) and instructs to send replies to the returned reverse_alias_address. It does not explicitly mention when not to use or list alternatives, but 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.