mail_createAPITokenV1

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

With no annotations, the description carries the full burden. It discloses that the plaintext token is returned only once and is never retrievable again, as well as the 10-token limit. This adds important behavioral context beyond the schema.

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; concise and front-loaded. No unnecessary words. The scope advice is presented clearly.

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?

Despite no output schema, the description covers creation purpose, token usage, unrecoverability, limits, and scope choices. Sibling tools are related but irrelevant to completeness. All essential context is provided.

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 coverage is 100%, providing baseline. The description adds meaning by explaining the scope options (`has_all_mailboxes` vs `mailbox_ids`) and that `name` is a human-readable label. This goes slightly beyond what the schema provides.

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 an API token for a mail order and explains the token's purpose (access to Hostinger Email API for mailbox management). It distinguishes from sibling tools like mail_revokeAPITokenV1 and mail_listAPITokensV1.

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 guidance on when to use `scope.has_all_mailboxes` versus listing specific mailboxes in `scope.mailbox_ids`. Mentions the maximum token limit per order (10). Does not explicitly state alternatives or when not to use, but context is sufficient.

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