cloud_create_ssh_key

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

The description only says 'Add an SSH public key' without disclosing behavioral traits such as whether duplicate keys are rejected, what happens on failure, or any side effects. No annotations are provided to compensate.

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 sentence, which is concise, but lacks structured detail. It is adequately front-loaded but too brief to be fully informative.

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?

Considering the tool has 3 parameters and a creation role, the description is insufficient. It provides no context about return values, error handling, or prerequisites, and the output schema is not shown.

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?

With 0% schema description coverage, the description adds no information about parameter semantics. The parameter names (name, public_key, labels) are self-explanatory but the description does not clarify expected formats, constraints, or defaults beyond what the schema states.

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 the action ('Add an SSH public key') and the resource ('to the project'), which distinguishes it from related tools like cloud_update_ssh_key or cloud_delete_ssh_key.

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, no prerequisites mentioned (e.g., valid key format, authentication), and no conditions under which this tool should not be used.

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