List paid TLS certificates

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description earns credit for adding what they don't: an auth/scope requirement (certificates:read) and a genuine interpretation caveat ('attention_required is not success'). It still says nothing about pagination or result size, which keeps it out of 5 territory.

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 action and scope, with no filler. The closing caveat 'attention_required is not success' is terse and slightly cryptic in isolation, but it is high-value and does not bloat the text.

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 output schema, the description compensates by enumerating the salient returned fields and by stating the required scope, which is sufficient for a zero-parameter read-only listing. The only real gap is pagination/result-size behavior, which is minor for this tool shape.

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 zero parameters, so per the rubric the baseline is 4. The description correctly introduces no parameter discussion, and the listed fields describe output rather than inputs, so there is nothing to compensate for.

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?

Specific verb (List) plus a precisely scoped resource ('customer-owned paid TLS certificate orders'), which implicitly separates it from the sibling list_free_certificates and from the single-resource get_certificate. It also enumerates the returned fields (EUR amount, validation/issuance state, renewal dates, bundle readiness), so an agent knows exactly what this resource yields without opening a schema.

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 states a prerequisite ('Requires certificates:read') but gives no when-to-use guidance and never routes the agent to alternatives such as get_certificate for a single cert or list_free_certificates for free ones. Usage is only implied by the verb 'List', which is the minimum viable level.

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