aap_delete_credential

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

Annotations already declare destructiveHint=true, but the description adds the confirmation token mechanism and the dual return states (confirmation prompt vs success JSON). This goes beyond the annotations and gives the agent actionable behavioral details. No contradictions.

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 and well-structured: a one-line purpose, then args, then returns. Every sentence earns its place, and the dangerous nature is front-loaded with 'DESTRUCTIVE - requires confirmation.'

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?

The two-step confirmation flow is adequately explained, and the output is just a string so no detailed return schema is needed. It is complete enough for an agent to understand the tool's behavior, though it omits potential error cases or prerequisites beyond confirmation.

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 carries the full burden. It explains both parameters: credential_id as the target ID and confirmation_token as the token from the first call. This adds meaning beyond the raw schema types, though it could be slightly more detailed about how the token is obtained.

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 credential', which is a specific verb + resource that clearly distinguishes this from sibling delete tools for other resources. The 'DESTRUCTIVE' warning adds important scope clarification.

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?

Provides clear context about the two-step confirmation flow ('requires confirmation', 'Token from first call') and return behavior. However, it does not explicitly name alternatives or state when not to use this tool, though the purpose is self-evident from the resource type.

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