Delete a provider credential

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

Annotations already mark the tool as destructive, so the description adds value by disclosing that the previous state is snapshotted before the write and that nuvio_undo can revert the change. It does not contradict the annotations, and the confirm-based preview behavior is covered in the schema.

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 two short sentences with no filler. The primary action is front-loaded, and the second sentence adds a useful safety detail about undo without bloating the text.

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 3-parameter destructive tool, the combination of annotations, schema, and description is largely sufficient. The description adds the undo/snapshot context, while the schema documents the confirm requirement and profile_id default. A slightly fuller mention of the preview-without-confirm behavior would make it fully 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 description coverage is only 33%, so the description should compensate by clarifying parameters. It only loosely maps 'provider credential' to the provider parameter and 'profile' to profile_id, without explaining valid provider values or the role of confirm beyond what the schema already says.

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'), a specific resource ('stored provider credential'), and a location ('from a profile'). This clearly distinguishes the tool from sibling tools like nuvio_set_provider_credential and nuvio_list_provider_credentials.

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 explains what the tool does but gives no explicit guidance on when to use it versus alternatives such as nuvio_set_provider_credential. It does not mention prerequisites, exclusions, or context where deletion would be inappropriate.

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