aap_delete_user

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

Annotations already mark the tool as destructive, but the description adds valuable context: a confirmation token is required from a first call, indicating a two-step confirmation workflow. This goes beyond the structured hints and clarifies expected behavior.

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 concise and front-loaded with the purpose and a clear DESTRUCTIVE warning, followed by a compact parameter list. Every line contributes necessary information without waste.

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 destructive tool, the description omits a critical workflow detail: the first call likely returns a confirmation_token, and a second call is required to complete the deletion. The phrase 'Token from first call' is insufficient for an agent to confidently execute the two-step process; the description is incomplete for safe usage.

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 description lists both parameters with brief annotations, and 'Token from first call' adds meaning beyond the schema's bare title. However, it does not explain how to obtain the token or the format expected, so the added value is limited.

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 opens with 'Delete an AAP user,' a specific verb and resource, clearly distinguishing it from sibling delete tools by naming the target. It also flags the destructive nature, which adds precision.

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 states that deletion requires confirmation and mentions a token from the first call, implying a two-step process. However, it does not explicitly compare to alternative tools or state when not to use this tool, leaving usage guidance thin.

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