Application Password löschen

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the delete action, without mentioning irreversibility, required permissions, or side effects (e.g., revoking existing tokens). The destructive nature is implicit but not elaborated.

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, complete sentence with no redundant words. It is maximally concise and front-loaded with the core action and object.

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?

As a destructive admin operation, the description lacks essential context: when to use it, post-deletion consequences, and the role of the optional userId. Without annotations or an output schema, the minimal text does not fully equip an agent to deploy the tool correctly.

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 documents both parameters (uuid and userId) with descriptions, giving 100% coverage. The description adds no extra parameter meaning, so the baseline of 3 applies for high schema coverage.

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 action ('Löscht ein Application Password' = 'Deletes an application password') with a specific verb and resource. It distinguishes from sibling tools like admin_create_app_password and admin_list_app_passwords by indicating the delete operation.

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?

No information is provided about when to use this tool versus alternatives, such as when an application password is compromised or no longer needed. There are no prerequisites, exclusions, or references to related tools for context.

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