ssh_reconnect

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

Annotations already cover read-only, idempotent, and non-destructive hints. The description adds valuable behavioral context: only the selected connection is reloaded/validated, other connections are not affected, and SSH credentials are private server-side configuration. It does not contradict the annotations and supplements them meaningfully.

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?

Four compact sentences, each with a distinct purpose: action, scoping guarantee, credential privacy constraint, and alternative-tool routing. The primary action is front-loaded and there is no extraneous or redundant text.

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 single-parameter tool with no output schema, this description covers the action, scope, credential handling, and fallback tool selection. It does not detail validation failure behavior, but that is not essential for correct invocation given the annotations and schema richness.

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 fully documents the sole parameter with 100% coverage. The description enhances this by specifying that the alias must be an exact configured server alias and directs the agent to ssh_list_servers when one is not available, adding practical sourcing guidance beyond 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?

States a specific action (reload and validate) on a specific resource (selected server configuration). It distinguishes itself from siblings by explicitly scoping to the selected server and noting that other connections are unaffected, making the tool's role clear among the listed SSH tools.

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?

Provides explicit routing guidance to ssh_list_servers when the user has not supplied an exact configured alias, and includes a firm instruction to never ask for a password. It could further contrast against other sibling tools, but the most relevant alternative is addressed and the usage context is clear.

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