aap_delete_group

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

Annotations already declare destructiveHint=true, and the description adds the important behavioral detail that confirmation is required, with a token from the first call needed for the second call. This goes beyond the annotation by explaining the confirmation mechanism, though it doesn't specify what the first call returns beyond the implied token.

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 brief and well-structured: a single sentence stating purpose and warning, followed by a concise parameter list. No unnecessary words or repetition.

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 tool has a destructive two-step confirmation flow, and the description does explain the token requirement, which is crucial. However, it doesn't describe the behavior of the first call in detail (e.g., whether it returns a token or queues the deletion), nor any error conditions. An output schema exists, so return values are not required, but the workflow is still somewhat underspecified.

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 lists both parameters with brief explanations: group_id as 'Group ID' (minimal, tautological) and confirmation_token as 'Token from first call' (adds meaningful context about the workflow). This is helpful but lacks depth, such as how to obtain the token or what values are valid.

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 'Delete a host group from an AAP inventory' clearly states the specific action (delete), resource (host group), and system (AAP inventory). This distinguishes it from sibling tools like aap_remove_host_from_group, which removes a host rather than deleting the group itself.

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 clear context by noting the destructive nature and the confirmation requirement, which implies a two-step usage process. However, it does not explicitly state when to use this tool over alternatives or mention any exclusions, though the purpose is specific enough that alternatives are obvious.

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