get_cert_certificate

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

Discloses that private key is not returned, setting clear expectations. No annotations provided, so description carries full burden; it covers the main behavioral trait. Could add more about permissions or errors, but sufficient for a simple read tool.

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 concise sentences with front-loaded purpose and important exclusion detail. No filler or redundancy.

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 single-parameter get tool with no output schema, the description adequately covers the return value (metadata and public key, not private key). Could mention error handling or response format, but not essential given context.

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?

Single parameter 'certificate_id' is fully described in the schema (100% coverage). Description does not add additional meaning beyond the schema, so baseline score of 3 applies.

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?

Clearly identifies the action (Get details), the resource (SSL/TLS certificate by ID), and specifies what is returned (metadata and public key material) and notably what is NOT returned (private key), distinguishing it from other get tools.

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?

Implies usage for fetching a specific certificate by ID, but no explicit guidance on when to use this vs sibling tools like 'get_cert_auto_certificate' or when not to use it.

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