provider_delete_certificate_library_item

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not carrying the safety burden. It nonetheless adds real context beyond the annotations: the in-use deletion constraint and the deprecated misspelled alternate path with its removal version, which affects how an agent might target the endpoint.

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 constraint is front-loaded, but the first two sentences are redundant ("Remove certificate library item." then "Delete the specified certificate library item."), and the misspelled-path aside is verbose for a deprecated route. Trimming would sharpen it without losing information.

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 one-parameter destructive delete with full annotation coverage and no output schema, the description supplies the key operational fact (in-use items cannot be deleted) plus the endpoint. It stops short of explaining failure behavior or what happens to existing consumer references, but nothing essential to invoking it 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?

Schema description coverage is 100% and there is a single required "id" parameter, so the baseline is 3. The description's path template shows that id is the certificate library item identifier in the URL, which adds only marginal clarity over the schema.

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 states a specific verb (delete/remove) and a precise resource (certificate library item), which separates it from siblings like provider_delete_certificate (trusted certificates) and provider_update_certificate_library_item. It does not explicitly name those siblings, so it falls short of a 5.

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?

"Only items that are not in use can be deleted" is a genuine precondition that tells the agent when the call will fail, but no alternatives are named (e.g., querying consumer refs first via provider_query_cert_library_item_consumer_refs, or using provider_delete_certificate for a different resource). Usage is implied rather than routed.

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