nexo_credential_delete

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

No annotations are provided, so the description carries the burden. It discloses deletion behavior and the conditional, but lacks details on irreversibility, permissions, or side effects. While 'delete' implies a destructive action, more explicit behavioral context would be beneficial.

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 sentence that front-loads the core purpose ('Delete credential(s)') and efficiently adds the conditional. No unnecessary words; every part earns its place.

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 no output schema or annotations, the description covers the essential behavior and conditional. However, it does not mention return values, error cases, or what happens after deletion. A slightly more complete description would improve context for an AI agent.

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 both parameters having clear descriptions. The tool description does not add significant meaning beyond the schema; it essentially restates the conditional from the 'key' parameter description. Baseline 3 is appropriate as schema covers the parameters well.

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 (delete) and the resource (credential(s)), with a conditional for deleting all if no key is provided. It differentiates from sibling tools like nexo_credential_create, nexo_credential_get, nexo_credential_list, and nexo_credential_update by focusing on deletion.

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 usage by stating the conditional behavior (deleting all if no key), but it does not explicitly specify when to use this tool over alternatives or provide prerequisites. The purpose is clear enough for selection among credential-related siblings.

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