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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds the plan-tier constraint (Advanced SSL requires Business/Enterprise), which is genuinely useful context, but says nothing about the response shape or what AutoSSL statuses can be returned. With annotations carrying much of the load, a 3 is appropriate.

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?

Two short sentences plus a raw endpoint path. Most of it is front-loaded and useful, though the trailing 'GET /servers/{id}/webapps/{webapp}/ssl/advanced' restates information an agent does not need to invoke the tool.

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?

With no output schema, the description carries the burden of explaining return values, and it only names two fields (SSL method, AutoSSL status) without indicating possible values or shape. It is adequate to decide when to call, but thin on what comes back.

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% and both parameters (server_id, webapp_id) are documented in the schema with pointers to helper tools. The description adds no parameter-level detail, so the baseline 3 applies.

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 specifically what is retrieved: whether the webapp uses basic (one certificate) or advanced (one per domain) SSL, plus its AutoSSL status. The parenthetical definitions make the distinction concrete. It does not, however, differentiate itself from siblings like runcloud_get_webapp_ssl, which could plausibly return overlapping information.

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 call this versus runcloud_get_webapp_ssl, runcloud_install_letsencrypt_ssl, or runcloud_renew_ssl. The note that 'Advanced SSL is a Business/Enterprise feature' is a constraint on results, not usage direction, and no prerequisites are stated.

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