cwp_autossl_renew

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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose auth requirements, side effects on existing certificates, downtime, rate limits, or whether renewal is idempotent, leaving significant transparency gaps for a mutation tool.

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 front-loaded sentence with zero wasted words. It communicates the action and scope immediately without 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?

For a certificate-renewal mutation with no annotations and no output schema, the description is too sparse. It omits prerequisites, expected outcome, and behavioral side effects that an agent would need to invoke it confidently.

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 fully documents the single required 'domain' parameter (100% coverage). The description's phrase 'for a domain' is redundant with the schema and adds no format or validation meaning, so the baseline of 3 is appropriate.

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 resource ('SSL certificate') scoped to a domain. It is clear but does not explicitly distinguish the action from sibling tools like cwp_autossl_install or cwp_autossl_delete, leaving sibling differentiation to inference.

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 use this tool versus alternatives such as cwp_autossl_install or cwp_autossl_list. Prerequisites, timing, or conditions for renewal are not mentioned, so the agent receives no explicit usage context.

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