aap_delete_workflow_template

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

Annotations already mark the tool as destructive, and the description adds the crucial detail that confirmation is required, along with the confirmation token flow. This goes beyond the annotation by explaining the interactive confirmation mechanism.

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 well-structured with clear 'Args' and 'Returns' sections. Every sentence provides useful information without unnecessary fluff, making it easy to scan.

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 the destructive nature and confirmation flow, the description covers the essential steps and return types. It doesn't mention side effects beyond deletion, but the annotation and confirmation details make it sufficiently complete for an agent.

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 input schema has no description coverage for parameters, but the description explains that workflow_id is the template ID and confirmation_token comes from the first call. This adds essential semantics beyond the raw schema fields.

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 begins with 'Delete an AAP workflow template', clearly stating the action (delete) and target resource (workflow template). This is specific and distinguishes it from sibling delete tools targeting other resources.

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 explicitly indicates the two-step confirmation process ('requires confirmation') and the token parameter, giving clear context on how the tool should be used. However, it does not explicitly name alternatives or state when not to use this tool, which prevents a 5.

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