coolify_get_private_key

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get detailed information', implying a read-only operation, but does not confirm idempotency, discuss auth requirements, rate limits, or what happens if the key does not exist.

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 concise single sentence that front-loads the verb and resource. It is efficient, though it could be slightly improved by hinting at the required parameter or return value without adding much length.

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 retrieval tool with one parameter, the description is adequate but incomplete. It does not mention that the result is a private key object (no output schema), nor does it explain how to interpret the 'detailed information' or any error conditions. Given the large sibling set, a little more context for an AI agent would be helpful.

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 coverage is 100% (the UUID parameter is described in the schema). The tool description adds no additional meaning beyond the schema's property description. Baseline 3 is appropriate as the description neither harms nor significantly improves parameter understanding.

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 explicitly states the action ('Get') and the resource ('detailed information about a specific SSH private key'), clearly distinguishing it from sibling tools like 'coolify_list_private_keys' (which lists keys without details) and create/update/delete variants.

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. For example, it does not suggest using 'coolify_list_private_keys' first to obtain UUIDs, nor does it specify prerequisites or when not to use this tool.

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