stalwart_delete_api_key

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

With no annotations provided, the description carries the full burden and does well by explicitly stating 'Destructive — requires confirm=True'. It also clarifies the confirm parameter must be True to proceed, which is critical behavioral info beyond the schema's default false. Minor gap: it doesn't mention reversibility or effects on existing sessions, but the destructive nature is clearly disclosed.

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 extremely concise, using a clean two-line summary followed by a minimal Args list. Every sentence earns its place, and the structure is immediately scannable.

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 delete tool with 2 parameters and an output schema present, the description covers the essential context: destructive nature, required confirmation, and parameter provenance. It doesn't explain return values, but the output schema likely covers that. The lack of annotations is offset by the description's clear behavioral disclosure.

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 schema has 0% description coverage, so the description must compensate. It does by explaining api_key_id as 'key id (from stalwart_list_api_keys)' and confirm as 'must be True to proceed'. This adds practical meaning beyond the raw field names and types.

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 'Delete an API key' with a specific verb and resource, and it distinguishes the tool from siblings like stalwart_create_api_key and stalwart_list_api_keys by focusing on deletion. The arg list further clarifies that it takes an API key ID.

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 gives clear context that this is a destructive operation requiring confirm=True, and it implies usage with 'from stalwart_list_api_keys' for obtaining the ID. However, it does not explicitly state alternatives or when-not-to-use conditions, so it falls short of a 5.

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