Delete ACI Configuration

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

Annotations already provide destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the agent knows this is a destructive, non-read-only operation. The description adds no extra behavioral context such as irreversibility, cascade effects, or required permissions, so it adds no value beyond the annotations.

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, front-loaded sentence that clearly states the action, resource, and required parameter. 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?

For a simple delete operation with one parameter and no output schema, the description is largely sufficient. Annotations fill in the safety profile (destructive, idempotent). It could mention permanence or typical success response, but the simplicity and annotations make it fairly complete.

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 provides 100% coverage with a clear description of app_id ('The ACI app id whose configuration to delete'). The tool description also mentions 'by app id', but adds no additional semantic detail beyond what the schema already states.

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 uses a specific verb ('Delete') and identifies the resource ('ACI app configuration') plus the required identifier ('by app id'). It clearly distinguishes from sibling tools like create and list configurations, and from other delete tools like delete_aci_connection.

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 usage is implied: the tool is for deleting an ACI app configuration, and sibling names (create/list) suggest the lifecycle. However, there is no explicit guidance on when to use this over other delete-related tools (e.g., delete_aci_connection) or what prerequisites or permanent consequences exist.

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