Toggle SimpleLogin Alias

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

The description discloses key behavioral traits: disabling blocks all incoming mail without deleting the alias record. This adds context beyond annotations (destructiveHint=false, idempotentHint=true). It does not mention any side effects or permission requirements, but the annotations already provide a good safety profile.

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 sentences, the first immediately stating the verb and resource, the second adding context. No unnecessary words or repetition. Perfectly concise.

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 explains the tool's purpose and behavior, which is sufficient given the simple schema and presence of an output schema. However, the lack of parameter explanation (aliasId) is a notable gap that could lead to misuse or confusion.

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?

With schema description coverage at 0%, the description must compensate, but it fails to mention the aliasId parameter at all. It only implies the tool acts on an alias, leaving the agent to infer the parameter's meaning from the schema alone. This is inadequate for an agent to correctly use the tool.

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 verb 'toggle' (enable or disable) and the resource 'SimpleLogin alias', distinguishing it from sibling tools like alias_create, alias_delete, and alias_list. It provides a specific use case (blocking mail from abusive services) without deleting the alias.

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 implies when to use this tool (when a service abuses an alias) and mentions what it does not do (delete the alias record). However, it does not explicitly state when not to use it or suggest alternatives like alias_delete for permanent removal.

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