cloudflare_certificate_list

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

The description indicates it is a read operation listing certificates, but with no annotations, it fails to disclose potential side effects, rate limits, or pagination behavior. It adds some value by mentioning the types of certificates included.

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 sentences, front-loaded with the core action, no wasted words. Efficient and clear.

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?

No output schema exists, and the description does not explain what fields or structure the returned certificates have. It says 'shows all certificates' but omits details on output format, pagination, or limits. For a list tool, this is a gap.

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%, so baseline is 3. The description adds minimal extra meaning: it clarifies zone_id can be a name or hex, and status is an optional filter. This aligns with the schema but does not provide additional detail beyond what is already documented.

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 clearly states it lists SSL/TLS certificate packs for a zone, specifying the types (Universal SSL, Advanced, custom uploads). This distinguishes it from the sibling tool cloudflare_certificate_get, which likely retrieves a single 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?

No explicit guidance on when to use this tool vs alternatives. While the sibling name suggests cloudflare_certificate_get is for individual certificates, the description does not provide direct context or exclusions.

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