pve_renew_node_certificate

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Renew' implies a mutation operation, but the description doesn't specify whether this requires special permissions, whether it's reversible, what happens during renewal, or potential side effects. For a certificate renewal tool with security implications, this is a significant gap in transparency.

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 extremely concise with just three words, making it easy to parse. There's no wasted language or unnecessary elaboration. While it may be too brief for complete understanding, it's structurally efficient and front-loaded with the core action.

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 certificate renewal operation with security implications and no annotations or output schema, the description is inadequate. It doesn't explain what ACME certificates are, what 'node' represents in this context, what happens during renewal, or what the expected outcome is. The minimal description leaves too many questions unanswered for proper tool selection and invocation.

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%, so the schema already documents both parameters ('node' and 'force') adequately. The description doesn't add any additional meaning beyond what the schema provides about these parameters. This meets the baseline expectation when schema coverage is complete.

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 'Renew ACME certificate' states the action and resource but is vague about scope and context. It doesn't specify what 'node' refers to or what type of certificate is being renewed, making it less clear than ideal. While it distinguishes from siblings by focusing on certificate renewal, it lacks the specificity needed for full understanding.

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. The description doesn't mention prerequisites, timing considerations, or what happens if the certificate isn't due for renewal. With many sibling tools available, this lack of context makes it difficult for an agent to determine appropriate usage scenarios.

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