delete-pce-credentials

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it delivers. It explicitly states this is a WRITE OPERATION that changes PCE state, discloses idempotency, and warns about approval pauses in gated clients with the crucial guidance that the call has not failed and must not be retried while waiting. This is exemplary behavioral 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 compact and front-loaded: the core action is in the first sentence, followed by essential behavioral notes. Every sentence earns its place, covering action, idempotency, side-effect, and client-gating behavior without waste.

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 parameterless, no-output-schema tool, the description is complete. It tells the agent what is removed, what side effects occur, how to handle approval delays, and that failure is not implied. Nothing essential is missing.

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?

The tool has zero parameters, so the baseline is 4; no parameter semantics are needed. The description accurately reflects that the operation targets the current user's credentials without requiring additional inputs, which fully covers the parameter dimension.

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 uses a specific verb ('Remove') and a precise resource ('the current user's stored PCE credentials'), clearly distinguishing it from sibling tools like register-pce-credentials and check-pce-credentials-status. An agent knows exactly what operation this performs.

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 clearly establishes when this tool is appropriate: remove stored credentials for the current user. It also adds important usage context by noting the operation is idempotent and safe to call even when no credentials are stored, so the agent need not pre-check. It does not explicitly name alternatives, but for a simple delete operation the usage context is clear.

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