npm_renew_certificate

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

With no annotations, the description must disclose behavioral traits. It only says 'renew (re-request)' without noting side effects, authorization requirements, whether it replaces the certificate, or potential failure modes. This lack of context is insufficient 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?

The description is a single concise sentence with no redundant words. It gets straight to the point, making it highly efficient and front-loaded.

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 lack of annotations and output schema, the description should cover essential behavioral aspects. It does not mention what happens after renewal, whether the operation is synchronous, or any prerequisites. The one-liner leaves significant gaps for a tool that modifies a certificate.

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 has one parameter 'id' with no description. The description clarifies that 'id' refers to an existing Lets Encrypt certificate, which adds meaning beyond the raw schema. However, it provides no additional details about the id's format or how it should be obtained.

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 the specific verb 'Renew' and targets a clear resource: 'an existing Lets Encrypt certificate by id.' This distinguishes it from sibling tools like create, delete, and download certificate. The action is unambiguous.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of conditions (e.g., expiration) or explicit alternatives like 'Use npm_create_certificate for new certificates.' The word 'existing' implies a distinction, but it does not actively guide selection.

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