list_certificates

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

Missing annotations, so the description must convey behavioral traits. It indicates a read-only listing operation, which is correct, but provides no details on performance, pagination, or side effects. The simplicity of zero parameters partially mitigates this gap.

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?

Extremely concise: a single sentence that contains all necessary information without any fluff. Every word 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 simple list with no parameters, the description is functionally complete. However, it lacks contextual details such as whether the operation is read-only, what the output format is (no output schema), and how it relates to certificate-specific tools.

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?

The input schema has no parameters (100% coverage), so the description adds nothing beyond the schema. No opportunity to enrich parameter meaning exists.

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 the action ('list') and resource ('all SSL certificates in NPM'), making the purpose explicit. However, it does not differentiate from sibling list tools like 'list_proxy_hosts' or the specific 'get_certificate' tool.

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 guidance on when to use this tool versus alternatives (e.g., get_certificate for a single certificate, or renew_certificate for renewal). The description lacks context on typical use cases or prerequisites.

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