Delete Provider

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=false, so the safety profile is covered by structured data. The description contributes nothing beyond that — it does not say whether the delete cascades to clients, domains, or tokens, whether it is soft or hard, or what happens on a nonexistent id.

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?

It is technically brief, but the brevity comes from under-specification rather than economy of expression. There is no front-loaded scope statement or consequence warning that would earn a higher score for tightness.

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 destructive, irreversible-in-practice mutation with an undocumented required parameter and no output schema, the description should explain consequences and prerequisites. It omits deletion side effects, dependent-resource impact, and error behavior, leaving the agent to guess.

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?

There is one parameter (id) with 0% schema description coverage, so the description must carry its meaning and does not. It never states that the id identifies the provider, nor the expected format or whether it is the provider's own id versus a tenant/provider composite.

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?

Tautological: description restates name/title.

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?

There is no guidance on when to use this versus providers_get/providers_list to confirm existence first, or versus the tenant-scoped variants. The only cue that this is a removal operation comes from the name itself, not from any stated condition or alternative.

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