npm_renew_certificate

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

With no annotations, the description carries the full burden of behavioral disclosure, and it says nothing about whether renewal requires ACME/HTTP challenge completion, whether it replaces the existing certificate in place, whether the operation is asynchronous, or what permissions are needed. This is a meaningful gap for a mutating operation.

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 that front-loads the action and resource with zero filler or redundancy. Nothing could be removed 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 renewal tool with a fully documented schema, the definition is minimally viable, but with no annotations and no output schema it omits what happens on success or failure and any prerequisites. It is adequate rather than complete.

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 single certificate_id parameter is fully documented in the schema. The description adds no extra meaning (such as where to obtain the ID or whether it accepts a domain name instead), 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 states a specific verb (renew) and a specific resource (a Let's Encrypt SSL certificate), so the agent can tell it apart from npm_create_certificate or npm_delete_certificate. It stops short of explicitly naming sibling tools or clarifying how renewal differs from creation.

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?

There is no guidance on when to renew versus create a certificate, what prerequisites exist (e.g., the certificate must be near expiry or the domain must be validated), or what to do if renewal fails. The agent must infer usage entirely from the tool name.

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