Delete Credential

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

The annotations already disclose destructive behavior (destructiveHint=true) and idempotency (idempotentHint=true). The description adds the important trait of permanence ('Permanently delete'), which is more specific than the generic destructive hint and implies irreversibility. No contradiction with 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, concise sentence that front-loads the action ('Permanently delete') followed by the resource and scope. Every word contributes to clarity without fluff.

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 tool with one parameter, no output schema, and good annotation coverage, the description adequately conveys the core behavior. However, it could mention potential side effects (e.g., impact on agents using the credential) or clarify it targets the generic 'credential' resource versus provider or tool credentials, which would enhance completeness given the sibling context.

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 provides 100% coverage for the single parameter (credential_id) with description 'Credential id'. The description's phrase 'by id' adds minimal extra meaning, not specifying format or any further semantics. Baseline 3 is appropriate since the schema fully documents the parameter.

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 clearly states the action (permanently delete), the resource (credential), and the required identifier (by id). This distinguishes it from sibling tools like lyzr_credential_create, lyzr_credential_get, and lyzr_credential_update, making the tool's purpose unambiguous.

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 the tool is used when deleting a credential, but provides no explicit guidance on when not to use it or alternatives. Given the large number of similar delete tools (e.g., lyzr_delete_provider_credential, lyzr_delete_tool_credential), the description does not clarify which credential type it applies to, leaving room for confusion.

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