Delete Lyzr ACI Tool

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

The annotations (destructiveHint=true, readOnlyHint=false, idempotentHint=true) already declare the operation's destructive and non-idempotent nature. The description adds the crucial detail 'permanently,' which clarifies that deletion is irreversible—context beyond the annotations. It does not contradict 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, well-structured sentence with a clear verb, resource, qualifier, and parameter reference. No redundant words; it is maximally concise while retaining essential information.

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 fully documented parameter, the description provides all necessary context: it states the action, the target resource, the permanence, and the identifier. Annotations cover the destructive and idempotent behavior. No output schema exists, so return behavior is not required.

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 schema description covers 100% of the parameter ('The provider id to delete'). The tool description repeats this with 'by provider id,' providing minimal additional meaning. Since schema coverage is complete, the baseline of 3 is appropriate; the description adds no significant new parameter insight.

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 resource ('Lyzr ACI tool') with an important qualifier ('permanently') and the identifier ('by provider id'). It clearly distinguishes this from sibling tools like lyzr_delete_aci_connection or lyzr_delete_aci_configuration 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 by stating the resource and identifier, but it does not explicitly mention when to use this tool instead of alternatives, nor any exclusions. For example, it doesn't clarify that this is for Lyzr ACI tools specifically versus other delete operations, though the name and resource type provide some context.

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