private_key

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

Annotations include openWorldHint=true, indicating potential unknown side effects. The description mentions safety confirm for destructive ops, adding some context, but does not detail permissions, irreversible consequences, or other behavioral traits beyond CRUD.

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 extremely concise: a one-line purpose, action signatures, and a safety line. All information is front-loaded and no unnecessary words.

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 a 100% schema coverage, output schema present, and clear action signatures, the description is largely complete. Minor omission: no mention of response formats or errors, but these are covered by the output schema.

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%, so parameters are fully documented in the schema. The description adds value by grouping parameters per action (e.g., list(format?, page?, per_page?)), showing required vs optional, but does not explain parameter 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 clearly states it is a "Private key CRUD for SSH keys registered in Coolify." and explicitly lists each action with parameters, making the purpose very clear. It distinguishes itself from sibling tools which are high-level categories.

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?

Provides safety guidance for destructive operations (confirm) and reveals (reveal opt-in only). Implicitly guides when to use each action via the parameter signatures, but does not explicitly compare to alternatives or state when not to use.

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