ssh_key_bootstrap

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

With no annotations, the description carries the full burden and does a good job: it discloses the workflow, side effects (installing the public key, saving a profile), and prerequisites (password). It lacks details about idempotency, overwrite behavior, failure handling, or security caveats like where the private key is stored.

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 definition is a single front-loaded sentence that leads with the tool name and conditional, then lists the actions in order. It is dense but every clause is substantive, with no filler or repetition.

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 complex, six-parameter mutating tool with no annotations and no output schema, the description adequately covers the purpose and end-to-end workflow. It falls short of full completeness by omitting failure modes, security considerations, and what the tool returns after verification.

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 description coverage is 100%, so the schema already documents all six parameters thoroughly. The description only alludes to the saved profile and generated key, adding no parameter syntax or constraints beyond what is already in 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 states a specific verb (bootstrap) and resource (SSH key) and enumerates the exact steps: generating a local key pair, connecting via password, installing the public key, verifying key login, and saving a profile. It distinguishes itself from execution-oriented siblings by requiring only a VPS password and implying a one-time setup scenario.

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?

It gives a clear condition for use: 'If you only have a VPS password.' This tells the agent exactly when to choose this tool over key-based alternatives, though it never names a sibling tool explicitly or states 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.