List paid TLS certificate catalog

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the currency (EUR), the required 'certificates:read' scope, and the fact that only customer-visible catalog data is exposed. It stops short of describing pagination or result limits.

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?

Five sentences, front-loaded with the core purpose, and no filler. The enumeration of disclosed fields is dense but justified given there is no output schema to carry that information.

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 parameters, no output schema, and rich read-only annotations, the description carries the necessary remaining load: it enumerates the returned fields (validation level, CA brand, SAN limits, term, retail prices), states the currency, and states the auth scope. An agent has everything needed to call and interpret it.

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 tool takes no parameters, so the baseline for an empty input schema is 4. There is nothing for the description to clarify at the parameter level.

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 (List) and resource (paid TLS certificate products and final customer offers in EUR). The 'paid' qualifier and the note that certificates are 'portable and not limited to managed applications' implicitly distinguish it from siblings like list_free_certificates and the automatic-SSL family, though no sibling is named explicitly.

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?

The description implies this is a browsing/catalog tool used before quoting or ordering, and clarifies that only customer-visible data is returned. However, it never states when to use this versus get_certificate_catalog_product for a single product or quote_certificate for pricing, leaving the choice to inference.

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