delete-credential

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

Without annotations, the description must disclose behavioral traits. It states deletion and ownership requirement but fails to mention irreversibility, error handling, or side effects. This leaves the agent uninformed about the destructive nature beyond the name.

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 concise with two sentences and no wasted words. However, it sacrifices some useful behavioral information; still, it earns a 4 for lack of 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?

While the description states the operation and owner requirement, it lacks completeness on prerequisites like obtaining the credential ID and clientId. The tool relies on these parameters, and the description does not indicate how to retrieve them or handle errors. For a simple tool, it is minimally adequate but not complete.

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 covers both parameters with descriptions. The tool description does not add any parameter semantics beyond the schema, 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?

The description explicitly states the action ('Delete') and the resource ('credential'), and adds a condition ('You must be the owner'). This clearly distinguishes it from other delete tools like delete-execution or delete-workflow.

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 includes an ownership prerequisite but does not provide guidance on when to use this tool over alternatives (e.g., deactivating instead of deleting). The usage is straightforward for a delete operation, but more explicit context would help.

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