List Mail API Tokens

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

The description says only 'List API tokens for mail,' which implies a read-only operation, but no annotations are provided to confirm safety. It does not mention authentication requirements, whether token secrets are returned, pagination, or any other behavioral context. With no annotations, the description carries the full burden and fails to disclose adequate detail.

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 a single, concise sentence ('List API tokens for mail.') that conveys the essential purpose without waste. It is appropriately sized for a zero-parameter list operation, though it is terse.

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 tool is simple with no parameters and no output schema. The description states the action and resource, but does not specify what the returned list contains (e.g., token names, IDs, or full secrets). Since there is no output schema, a bit more detail about the return value would improve completeness, but the verb 'List' partially covers this.

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 tool has zero parameters and an empty schema. There are no parameter semantics to explain, and the description adds no conflicting information. The baseline of 4 applies because with no parameters, nothing further is needed.

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's purpose: 'List API tokens for mail.' It uses a specific verb ('List') and specifies the resource ('API tokens for mail'), which distinguishes it from sibling create/revoke token tools. However, it does not explicitly reference those alternatives, so it stops short of a perfect 5.

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 provides no explicit guidance on when to use this tool versus alternatives or any prerequisites. However, the simple verb and resource imply that it is used to view existing mail API tokens, so usage is implied rather than stated.

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