Download public free-certificate bundle

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantive context: it never decrypts, reconstructs, or returns a managed private key, and it states the certificates:read permission requirement. This is useful safety/authorization disclosure beyond the annotations.

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 tight sentences, front-loaded with the return contents before the negative constraints. Every sentence carries information, though the CSR/private-key sentence is slightly longer than strictly needed.

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 responsibly enumerates what is returned and what is deliberately excluded (private key), and it names the required scope. For a single-parameter read tool this is nearly complete.

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?

There is a single parameter with 100% schema description coverage, including the UUID pattern and a pointer to list_free_certificates. The description adds nothing about the parameter, 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 ('Retrieve') and precisely enumerates the returned resource ('public leaf, issuer chain, and full chain for one issued no-cost certificate'). The scope-limiting word 'only' cleanly separates it from sibling operations like download_certificate or 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?

Gives clear operational context: it requires certificates:read and that a customer_csr result is only deployable with the customer-retained private key. It stops short of naming which sibling to use instead when a managed private key is actually needed, only saying that path stays portal-only.

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