Delete ACI Custom App

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

The phrase 'permanently delete' conveys irreversibility, which aligns with and reinforces the destructiveHint=true annotation. However, beyond that, it does not disclose additional behavioral details like cascading effects, idempotency behavior, or permission requirements. Annotations already cover the destructive and idempotent nature, so the description adds minimal new context.

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, compact sentence that front-loads the action and target. Every word earns its place with no filler or redundant clichés.

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 straightforward delete operation with one required parameter, the description is adequate. It clearly states the action, the target resource, the identifier, and the irreversibility. No output schema is provided, which is acceptable for a delete tool. Minor gaps such as return behavior or error conditions are not needed given the simplicity and the existing annotations.

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 only parameter, app_id, is fully described in the schema ('The ACI custom app id to delete'), and the description simply repeats 'by id'. With 100% schema coverage, the description provides no additional parameter meaning beyond what the schema already offers.

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'), identifies the resource ('ACI custom app'), and states the identifier ('by id'). It clearly distinguishes from sibling tools like lyzr_delete_lyzr_aci_tool or lyzr_delete_aci_connection by naming the exact resource type.

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 implies usage—when you need to permanently delete an ACI custom app by its id—but it does not explicitly mention alternatives, prerequisites, or when not to use this tool. No exclusions or contrasting sibling tools are provided.

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