Bulk Delete Tool Credentials

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is clear. The description adds little beyond restating the batch nature; it does not disclose additional effects like cascading deletions or reversibility, but with annotations present, this is an acceptable baseline.

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?

A single, tightly-constructed sentence with no redundant words. Effectively communicates the core action and scope.

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 one-parameter delete tool with annotations covering destructiveness, the description is sufficient. It lacks only an explicit statement about irreversibility, which is already implied by the destructiveHint annotation.

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 100% ('Tool credential ids to delete'), and the description's 'by id' merely paraphrases the parameter. No additional semantic detail is given, so the baseline of 3 is appropriate.

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 ('multiple tool credentials') with a scope ('by id in one call'). It clearly differentiates from the sibling single-delete tool (lyzr_delete_tool_credential) by emphasizing 'multiple' and batch operation.

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 phrase 'in one call' provides clear context for batch deletion, implying usage when deleting multiple credentials at once. It does not explicitly name the alternative single-delete sibling, but the bulk/multiple framing makes the appropriate scenario clear.

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