timeweb_create_ssh_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 disclosing behavioral traits. It only states 'Create a new SSH key' and fails to mention any side effects, required permissions, validation rules, uniqueness constraints, or response format.

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, concise sentence with no unnecessary verbiage. It is appropriately brief and front-loaded, focusing on the core action.

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?

The tool has a simple schema but lacks annotations and an output schema. The description is too minimal to be complete: it does not explain the relationship of the SSH key to servers, the expected input format beyond the schema, or what the agent should expect upon success.

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?

The schema description coverage is 100%, so the parameters are well-documented in the schema itself. The description adds no additional parameter semantics, confining itself to the baseline expected when the schema provides full descriptions.

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 'Create a new SSH key' directly restates the tool's name 'timeweb_create_ssh_key' without adding any new information about the tool's purpose, scope, or behavior. It is essentially a tautology.

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?

The description provides no guidance on when to use this tool versus alternatives such as 'timeweb_add_ssh_key_to_server' or 'timeweb_list_ssh_keys'. There are no prerequisites, scenarios, or exclusions mentioned.

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