delete_credential

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is destructive. However, the description adds no behavioral context beyond the annotations—it does not mention irreversibility, permissions, or what happens after deletion, so it fails to provide additional transparency.

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 extremely terse (3 words) but is under-specified and redundant. It does not earn its place because it merely repeats what the tool name already conveys, making it a waste rather than a concise, value-adding explanation.

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?

Given the destructive nature of the operation and the absence of an output schema, the description offers minimal context. It does not explain the effects of deletion, expected return values, or any constraints, leaving the agent with an incomplete picture for a potentially impactful action.

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% (the 'id' parameter has a meaningful description). The description itself does not expand on parameters, but the schema already handles the semantics, so baseline 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?

Description 'Delete a credential.' is a direct restatement of the tool name 'delete_credential' without adding any new information. It is a tautology that does not differentiate from siblings like update_credential or get_credential beyond the verb.

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 such as update_credential or deactivate_workflow. There are no stated prerequisites, side conditions, or exclusions, leaving the agent without context for appropriate selection.

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