Delete Provider Credential

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

Annotations already indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=true. The description adds the word 'permanently', which emphasizes irreversibility and provides context beyond the raw annotations. It does not contradict annotations and offers useful behavioral context for a destructive operation.

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, front-loaded with the action, and contains no extraneous words. It is perfectly sized for a simple delete operation.

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?

This is a simple one-parameter delete tool with comprehensive annotations and no output schema. The description, combined with the schema and annotations, provides adequate context for an agent to select and invoke the tool. It does not elaborate on success/failure behavior or prerequisites, but these are not essential for task selection.

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%, with credential_id described as 'The credential id to delete'. The description's 'by id' matches the schema but adds no new meaning. Since the schema fully documents the parameter, a baseline score 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 clearly states the action (permanently delete) and resource (provider credential) with the identifier method (by id). It is specific but does not explicitly distinguish from sibling tools like lyzr_credential_delete or lyzr_delete_tool_credential, though the resource type is named.

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?

No guidance is provided on when to use this tool versus alternatives. With many credential-related delete tools among siblings, a note specifying that this is for provider credentials and not other credential types would be helpful. The description only states what it does, not when to choose it.

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