Add host

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so openness to network is covered, but the description adds nothing: it doesn't say whether the host is persisted to a config/inventory file, how password vs. password_ref vs. identity_file interact, or what happens on duplicate alias. No contradiction with annotations, but zero added behavioral context for a mutation with 10 parameters.

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 one short sentence, but the brevity is under-specification rather than efficiency; there is nothing front-loaded about behavior, scope, or parameters.

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 10-parameter write operation with no schema descriptions and no output schema, the description supplies none of the missing context an agent needs to call it correctly or predict its effects.

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% across 10 parameters, including ambiguous ones like params_json, password_ref, known_hosts_file, and proxy_command. The description provides no semantics for any of them, leaving the agent with property names only.

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?

"Invoke the add_host operation" only restates the tool name and title; it names no resource beyond the alias 'host' and gives no scope. It does not distinguish this from siblings like tunnel_manager_load_inventory, tunnel_ingest_hosts, or tm_remote_copy_ssh_config, all of which also bring hosts into the system.

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 versus loading an inventory or ingesting hosts, and no prerequisites (e.g., needing existing credentials or a reachable SSH target) are stated. The agent must infer everything from the name alone.

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