sync_host_ssh_key

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

With no annotations, the description carries the full behavioral burden and provides none of it. It does not state what 'sync' mutates, where the key is synced from/to, whether it is destructive or overwrites existing keys, or what permissions are required.

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?

It is short, but that brevity is under-specification rather than conciseness — there is no front-loaded useful content because there is no content at all.

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 mutation-style tool with zero annotations, no output schema, and an undocumented required parameter, the description is entirely inadequate. An agent has no basis to invoke it correctly.

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 0% and the single parameter 'id' is completely undocumented in both schema and description. The description gives no clue what the id refers to (host id? key id?) or its expected format.

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 'Sync host SSH key' essentially restates the tool name without adding any differentiating detail. It names a verb (sync) and a resource (host SSH key), but siblings like generate_host_ssh_key, get_host_ssh_key, update_host_ssh_key, and delete_host_ssh_key make the distinct purpose of 'sync' unclear — sync from what to what?

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 whatsoever on when to use this versus the sibling SSH key tools (generate, get, delete, update). No prerequisites, no context, no exclusions are provided.

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