list_client_certificates

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

No annotations are provided, so the description carries the full disclosure burden, but it only restates the list operation and the mTLS domain. It does not disclose pagination, response format, required permissions, or the zone-vs-account scope of the listing, which is material for an agent.

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?

A single efficient sentence with no wasted words, and the 'for mTLS' qualifier earns its place by narrowing the resource type. It could have used the available space to clarify scope, but it is not padded or buried.

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 tool with no output schema and no annotations, the core call shape (list certificates for a zone, scoped by zone_id) is recoverable from the description plus schema. However, the zone-vs-account ambiguity versus list_account_mtls_certificates and the absent return-format info leave the definition adequate but not 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?

Schema description coverage is 100% and the single required zone_id is already documented, so the baseline of 3 applies. The description adds no parameter-specific meaning; its only contribution is domain context for what kind of certificates the zone_id refers to.

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 names a specific verb and resource ('List client certificates') and adds the mTLS domain, which meaningfully narrows the resource type. However, it does not distinguish this from the similarly named sibling list_account_mtls_certificates, so an agent must infer zone-scope from the schema rather than the description.

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 when-to-use or when-not-to-use guidance, and no alternative tool is named. With roughly 230 siblings including multiple certificate-listing tools (list_custom_certificates, list_origin_ca_certificates, list_account_mtls_certificates), the lack of any routing cue leaves an agent to guess.

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