provider_add_certificate_library_item

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

Annotations already declare readOnly=false, idempotent=false, destructive=false and openWorld=true, so the safety profile is covered. The description adds only the raw REST path; it says nothing about whether duplicate aliases are rejected, what permissions are required, or how private key material is handled at the API level.

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?

One short sentence plus the endpoint path, front-loaded with the verb and resource. The raw HTTP path adds little for an agent but is not noisy enough to penalize heavily.

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 mutation with a well-described nested body schema and annotations that carry the safety hints, the essential calling information is present. Missing are the effects of the write (duplicate handling, response shape) which no output schema covers.

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 the nested body properties already document privateKey, privateKeyPassphrase, certificate, description and consumerCount. The description adds no further meaning, so the baseline 3 applies.

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 and resource: 'Add an item to the certificate library', which separates it cleanly from the get/update/delete certificate library siblings. It does not explicitly name those alternatives or explain how it differs from provider_add_consumer_ref_to_cert_library_item, so it stops short of full differentiation.

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?

No statement of when to use this versus the sibling library operations (get, update, delete, add_consumer_ref) or what a caller needs before invoking it. The agent must infer the context entirely from the name.

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