provider_delete_certificate

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description adds the semantic framing 'revoke trusting', which clarifies what is destroyed (the trust relationship, not the certificate itself), but says nothing about downstream impact on deployments, required permissions, or error conditions.

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?

Two short lines, purpose front-loaded, zero filler. The raw HTTP verb and route add little for an agent but follow the standard pattern of this tool family and don't obscure the intent.

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?

A destructive, open-world mutation with no output schema and one weakly described parameter needs more than a restated endpoint. Missing are the consequences of revocation, whether existing consumers of the certificate are affected, and what an agent should verify before calling.

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 nominally 100%, but the only description is the terse '(path)', so the schema does not actually explain whether trustedCertificate is an ID or URN or its format. The description adds nothing further, so per the high-coverage baseline this lands at 3.

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?

States a specific verb+resource ('Revoke trusting specified certificate') that an agent can map directly to the operation. It doesn't distinguish itself from near-siblings such as provider_delete_certificate_library_item or provider_trust_certificate, which remains the only gap.

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 contains no when-to-use or when-not-to-use guidance and names no alternatives. There is no mention of prerequisites (certificate must first be trusted, must not be in use) that would help pick between the delete and trust/query siblings.

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