Retrieve or create the account's unrestricted MailKite API key (mk_live_…) using a management session token. First call generates the key for authenticated use.
Get the account's unrestricted API key (mk_live_…). Read-or-create: the first call mints it. Requires a management session token.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.20.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description says 'Read-or-create: the first call mints it,' implying a state-changing side effect, which directly contradicts the readOnlyHint=true annotation.
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?
Concise and grammatically sound, with the key detail upfront. The Windows-style ellipsis is slightly informal but does not harm clarity.
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?
Self-contained given the zero-parameter schema: it names the resource, the format, the precondition, and the read-or-create behavior. Only the contradiction with the readOnly annotation prevents a perfect score.
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 parametersched, so the schema cannot clarify anything. The description adds contextual meaning about the key and behavior, but there are no parameter semantics to clarify.
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?
Clearly states the tool retrieves the account's unrestricted API key (mk_live_…), which distinguishes it from sibling tools like rotate_api_key or scoped-key creation.
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?
Gives a clear usage context: obtain the unrestricted key with a management session tokencing. It implies when to use it versus scoped or rotated keys, though it does not name alternatives explicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.