credentials_remove

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

With no annotations, the description alone must carry behavioral disclosure. It does disclose the destructive operation and the exact-URL matching rule, but it does not state what happens when no matching credential exists, whether removal is permanent, or any error/edge-case behavior.

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, front-loaded sentence with no filler. Every word contributes: remove, credential, local store, and exact URL match.

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?

This is a simple one-parameter tool with an output schema available, so the description provides enough context for correct invocation. The only notable gap is the lack of detail about the no-match case, but this is minor for a straightforward deletion operation.

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 input schema only declares 'url' as a required string with no description, so the phrase 'by exact URL match' adds meaning that is not present in the schema. It tells the agent that partial or normalized URLs will not match, which is valuable for a single-parameter tool.

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 action ('Remove'), a clear resource ('credential entry'), and a scope ('local store') with an exact-match constraint. This distinguishes it from sibling credentials_save, credentials_list, and credentials_check without needing any additional context.

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 intended use is implied by the action and resource, so an agent can infer that this tool is for deleting stored credentials rather than saving or checking them. However, there is no explicit guidance about when to prefer this over alternatives, nor any mention of prerequisites or side effects.

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