provider_update_certificate_library_item

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

Annotations already declare readOnly=false, idempotent=true and destructive=false, so the safety profile is covered. The description adds useful behavior context (only alias/description are effectively editable, plus a deprecated alternate path) but omits what happens to body fields it says are not editable.

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 opening sentence is immediately repeated in near-identical form ('Update the specified certificate library item. Updates the specified certificate library item.'), wasting the front-loaded position. The deprecation note and raw HTTP path are useful but could be trimmed to one line.

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?

With full schema coverage and annotations covering safety, the description covers the essentials for a simple update. However, it lacks any mention of response behavior or failure modes, and its editability claim conflicts with the required 'certificate' field, leaving an agent uncertain about a valid body.

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 coverage is 100%, so the baseline is 3. The description contributes a real constraint (editability limited to alias and description), but that statement sits awkwardly against the schema, which marks 'certificate' as required in the body, creating ambiguity about what must actually be sent.

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 and resource (update a certificate library item) and even names the affected fields. It is unambiguous without opening the schema, though it does not differentiate itself from nearby siblings like provider_update_certificate or provider_replace_cert_library_item_consumer_refs.

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?

Usage is only implied by the verb 'update' — an agent can infer this mutates an existing item rather than adding or deleting one. There is no explicit statement of when to choose this over provider_add_certificate_library_item or provider_update_certificate, and no prerequisites are given.

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