renew_acme_certificate

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds 'triggers the renewal process,' hinting at an action that may involve external ACME interactions, but it doesn't expand on side effects, asynchronous behavior, or failure states. No contradiction with annotations.

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, front-loaded sentences with no filler. The purpose is stated immediately, and the second sentence reinforces the action without redundancy.

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 tool's low complexity (1 parameter, 100% schema coverage, output schema present, annotations provided), the description is largely sufficient. The only meaningful gap is lack of explicit differentiation from the sibling 'renew_certificate,' but the name itself conveys the ACME specificity.

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?

The schema already provides complete coverage for the single parameter (id) with description 'Certificate ID to renew (from search_acme_certificates).' The tool description adds no additional parameter semantics beyond what the schema states, 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?

The description clearly states the action: 'Renew an existing ACME certificate' and 'Triggers the renewal process for a previously issued certificate.' This distinguishes it from the sibling 'renew_certificate' (generic) and 'issue_acme_certificate' (initial issuance vs renewal).

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?

It establishes clear context: renewal is for previously issued certificates, implying it's not for new issuances. However, it doesn't explicitly mention alternatives or when to use another tool (e.g., renew_certificate for non-ACME certs). It also doesn't state any prerequisites or caveats.

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