Reissue Wordpress SSL

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

Beyond the annotations (non-read-only, idempotent, non-destructive, closed-world), the description discloses a rate limit ('Once per 5 minutes per site'), a DNS prerequisite, and the blast radius (domain plus www host). It does not say what the call returns or what a failure looks like, but the added operational context is substantial.

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?

Three short sentences, zero filler, with the action and scope front-loaded before the trigger condition and the rate-limit constraint. Every sentence carries distinct 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 two-parameter mutation with no output schema, the description supplies the trigger, prerequisite, and throttling behavior an agent needs to call it correctly. Only the expected outcome (what success or failure signals) is left unstated, which is a minor gap.

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 coverage is 100%, so both `domain` and `dry_run` are already documented in the schema, making 3 the baseline. The description reinforces that `domain` must resolve to the site but adds no syntax or format detail beyond that, and never mentions `dry_run`.

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 gives a specific verb and resource: 'Restart SSL certificate issuance for a Cloud for WordPress site', and clarifies the scope covers both the domain and its www host. It does not name a sibling tool it must be distinguished from (e.g. get_ssl_bundle or retry_cloudflare_domain), so it stops short of full differentiation.

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 states the precise trigger condition ('when `wordpress.site.ssl.issued` stays false') and a hard prerequisite ('The domain must point at the site'), which is exactly the context an agent needs before calling. It does not mention alternatives or when not to use it, so it is clear but not exhaustive.

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