authentik_delete

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

With no annotations, the description carries the full burden. It explicitly warns that the action is destructive and irreversible, which is crucial. It also explains the help mechanism. It lacks details on authorization requirements or rate limits but covers the key behavioral trait of irreversibility.

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 very concise: three sentences plus an example. It is front-loaded with the key behavioral warning ('destructive, irreversible'). Each sentence adds value, and the example clarifies usage. No wasted words.

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?

Given no output schema and no annotations, the description is somewhat complete: it explains the destructive nature, the help command, and provides an example. However, it lacks details about return values, error handling, and what specific resources can be deleted beyond the example. It is adequate but could be more thorough.

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 description coverage is 0%, so the description must compensate. It only explains that operation='help' lists operations and gives an example with 'DeleteUser' and 'id', but does not elaborate on available operation values or the structure of params beyond being a JSON object. This is insufficient for an agent to correctly invoke the tool without additional discovery.

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 deletes Authentik resources and emphasizes it is destructive and irreversible. It distinguishes itself from sibling tools like authentik_read and authentik_write by specifying delete operations. The purpose is unambiguous.

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 a how-to-use pattern, including calling operation="help" to list available operations and giving an example. However, it does not explicitly state when to use this tool versus alternatives like authentik_write or authentik_admin, though the deletion context is clear.

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