update_certificate

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

The parenthetical '(idempotent)' merely echoes the existing idempotentHint=true annotation, adding no new behavioral context. The description does not disclose whether changes require an apply step, prerequisites, or any side effects, relying entirely on annotations that are already present.

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 description is eight words in a single sentence, front-loaded with the verb and resource. Every word earns its place, with no filler or unnecessary detail.

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?

Given the full schema coverage, useful annotations, and presence of an output schema, the description is minimally adequate. However, it does not address the meaningful distinction from related tools like renew_certificate or generate_certificate, leaving a clarity gap in tool selection.

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%, with clear descriptions for all four parameters (PEM private key, certificate data, descriptive name, and ID source). The description itself adds no parameter-level detail beyond what the schema already provides, so the baseline score of 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?

The description uses a specific verb ('Update') with a clear resource ('certificate') and targeting mechanism ('by ID'). It distinguishes from sibling tools like create_certificate, delete_certificate, generate_certificate, and renew_certificate.

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 implies usage for existing certificates (vs creating new ones) but provides no explicit when-to-use/when-not-to-use guidance. It does not mention alternatives such as renew_certificate or generate_certificate, nor does it advise searching first, though the schema hints at this via the certificate_id description.

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