combell_ssl_certificates_get

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

Annotations already cover the safety profile with readOnlyHint and idempotentHint, so the description does not need to restate non-destructiveness. It adds a modest return expectation by mentioning subject alternative names, but it does not disclose not-found behavior, error semantics, or response shape beyond that.

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?

The description is a single front-loaded sentence containing the action, resource, lookup key, and a useful return detail. It has no filler and every phrase 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 one-parameter read operation with strong annotations, the description is largely sufficient: it identifies the resource, the input key, and one important output aspect (SANs). There is no output schema and no mention of all returned certificate fields or not-found behavior, but the tool's simplicity keeps this gap minor.

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 parameter sha1_fingerprint is already described as a SHA-1 fingerprint with a pointer to combell_ssl_certificates_list. The description merely repeats the fingerprint lookup relationship without adding format, encoding, or usage details beyond the schema.

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 states a specific retrieval action ('Get') on a precise resource ('SSL certificate') keyed by SHA-1 fingerprint, and adds that the result includes subject alternative names. This clearly differentiates it from the sibling listing tool combell_ssl_certificates_list as the single-certificate lookup variant.

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 when-to-use or when-not-to-use guidance is given, and no alternative tool is named in the description. The only usage hint is indirect: the parameter schema points to combell_ssl_certificates_list as the source of the fingerprint, implying this tool is for retrieving a specific certificate after listing.

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