mailkite_delete_scoped_key

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

Annotations already cover destructiveness and idempotency. The description adds useful behavioral context: revocation takes effect immediately and requires a management session token, which goes beyond what the annotations alone state. There is no contradiction with the annotation values.

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 three short sentences with zero filler. It front-loads the core action and then adds immediate-effect and authentication details, which is highly efficient for an AI agent.

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?

For a simple single-parameter destructive operation, the description is reasonably complete. It states the effect, timing, and auth requirement. A slightly fuller note about what happens after revocation (e.g., dependent credentials stop working) could be added, but the annotation and immediate-effect statement make the behavior clear.

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?

There is only one parameter and schema description coverage is 100%, so the baseline is 3. The description does not add explicit detail about the `id` parameter, but the resource is clear from the tool name and the phrase 'domain-scoped key'.

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 uses a specific verb ('Revoke') and resource ('domain-scoped key'), which clearly distinguishes this from sibling deletion tools such as delete_app_password, delete_sequence, and delete_domain. The purpose is instantly clear and not tautological.

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 the use case: revoke a domain-scoped key when it is no longer needed. It adds a prerequisite ('Requires a management session token'), but it does not explicitly contrast with related actions such as rotating a key or deleting an app password, so the selection guidance is only implied.

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