hostodo_add_ssh_key

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

With no annotations provided, the description fully carries the burden of transparency. It honestly discloses that the tool is a stub, does not perform the action, and returns a structured response. It also warns against sending secrets, enhancing behavioral clarity.

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 very concise with two sentences, no redundant information, and front-loads the key point that it is a stub. Every word earns its place.

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?

Given that this is a stub tool, the description is complete: it explains the stub nature, what it returns, and that no action is performed. No output schema is needed as the return is a simple structured response.

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% as all four parameters have descriptions in the input schema. The tool description adds a warning about not sending secrets but does not elaborate on parameter meanings or usage. Baseline 3 is appropriate as the schema already documents parameters.

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 tool is a stub that records demand and returns a coming_soon response, not actually adding an SSH key. It also mentions 'access: Add an SSH key', which conveys the intended purpose, and distinguishes from sibling tools like hostodo_list_ssh_keys or hostodo_remove_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?

The description implies the tool should not be used for actually adding an SSH key because it is a stub, but does not explicitly state when to use it or provide alternatives. The instruction 'Do not send secrets' is a useful guideline.

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