Download public TLS certificate bundle

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

Adds real behavioral context beyond the readOnly/idempotent annotations: exactly what the bundle contains, the guarantee that the private key is never included or reconstructed, and the required 'certificates:read' permission. These are the security and auth facts an agent needs before logging or forwarding the payload.

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?

Front-loads the purpose and the availability precondition in the first sentence. The long server-platform enumeration is somewhat verbose but supports the concrete portability claim, so it mostly earns its place.

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 one-parameter read operation with no output schema, the description covers the returned artifact (leaf/chain/full chain), the precondition, the permission requirement, and the private-key exclusion. Only minor gaps (e.g., response/encoding format) remain.

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 the single UUID parameter is fully documented there (including that it comes from list_certificates). The description only echoes the 'one owned order' framing without adding format or sourcing detail, so baseline 3 is appropriate.

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 (download) and precise resource (public leaf, chain, and full chain for one owned order), and the scope ('public', 'one owned order') distinguishes it from cert-management siblings like get_certificate and download_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 a clear precondition ('after download_available becomes true') and the ownership constraint, which tells the agent when the call is valid. It does not explicitly name alternative siblings (e.g., download_free_certificate) or state when not to use it, so it falls short of a 5.

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