site_ssl_update

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

No annotations provided, so description carries burden. Discloses it is a WRITE operation requiring confirm:true, indicates destructive nature by stating 'detach' and 'replace'. Lacks details on side effects or permissions but sufficient for basic understanding.

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?

Multiple concise sentences, all earning their place: purpose, API mapping, example use, detach method, confirmation requirement. No filler, front-loaded with key actions.

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?

Covers main intent and wildcard flow context. No output schema so could hint at expected results, but the description is sufficiently complete given tool complexity (9 params, write operation).

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 78%, description adds meaning: documents that certificate_id=null detaches, confirm must be true. Also provides workflow context. Some parameters like hsts, http2 remain described only in schema, but overall added value.

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?

Clearly states the tool attaches, replaces, or detaches SSL certificates and toggles HTTPS flags. Distinguishes from sibling tools like site_update or certificates_list by specifying the exact resource (SSL on existing site).

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?

Explicitly mentions use case for wildcard flow and how to detach (certificate_id=null). Says 'confirm:true required' indicating prerequisite. Does not explicitly say when not to use or compare with other tools, but context is clear.

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