Get free-certificate validation instructions

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), yet the description adds real value: it discloses what is NOT returned (no ACME challenge token, no provider credential) and names the required scope (certificates:read). This is context an agent could not derive from structured fields alone.

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?

Four short sentences, front-loaded with the primary action, each carrying distinct information (scope, DNS-branch behavior, negative returns, auth). Dense but every sentence earns its place; no filler.

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 itself explains the return content (durable CNAME delegations for external DNS) and the auth requirement, which is exactly what an agent needs to call and interpret this read tool correctly.

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?

Only one parameter exists and the schema documents it at 100% coverage, including format and the sibling that produces it. The description adds no additional parameter-level detail, so the schema-baseline of 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?

States a specific verb ('Read') and a precisely scoped resource ('current DNS validation instruction for one owned no-cost certificate request'). The 'no-cost certificate request' framing cleanly separates it from the paid-certificate sibling get_certificate_validation and from get_free_certificate.

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?

The description implies usage (fetching validation instructions after a free-certificate request) and explains branch-dependent behavior for VPSnet-hosted vs external DNS, but never states when to prefer this over siblings such as recheck_free_certificate, recheck_certificate_validation, or get_free_certificate.

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