acedatacloud_delete_credential

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

With no annotations provided, the description carries the burden of disclosing safety-critical behavior. It clearly states the operation is irreversible and requires explicit confirmation, which helps an agent avoid destructive mistakes. It does not detail authorization requirements or downstream effects, but covers the most critical risk.

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 only two short sentences, front-loading the core purpose and immediately stating the key safety/confirmation requirement. Every word earns its place with no redundancy.

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 two-parameter destructive operation with a rich input schema and output schema, the description provides essential context: what it does, that it is irreversible, and that confirmation is mandatory. It is slightly thin on when to choose delete over rotate or update, but that is reasonably inferable from sibling tool names.

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% and already defines credential_id as 'Credential UUID' and confirm as 'Must be true to revoke the credential.' The description's 'requires confirm=true' adds little beyond what the schema states, so the 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 'Revoke an API credential' uses a specific verb and resource, clearly identifying the operation. It naturally distinguishes from sibling tools like create_credential, update_credential, rotate_credential, and get_credential.

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 delete/revoke use case and mentions the important requirement that confirm=true must be provided. However, it does not explicitly state when to prefer revoking over rotating or updating a credential, nor does it name alternatives.

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