connect

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

With no annotations, the description carries the full behavioral burden. It does disclose one valuable trait: an empty password triggers a local popup so the secret never enters the conversation. However, it omits authentication requirements, whether the session persists, and failure/interactive-prompt behavior.

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?

Two tight sentences with the core action front-loaded and the password caveat immediately after. The parenthetical rationale is short and earns its place by explaining why.

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?

An output schema exists, so return values need not be described. Still, for a session-establishing tool with zero annotations and 0% schema coverage, the description leaves lifecycle questions open: relation to 'reconnect'/'disconnect', auth mode, and what happens on failure.

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 5 parameters, so the description must compensate and only partially does. It clarifies 'name' (router identifier) and 'password' (leave empty for prompt), but 'host' — the sole required parameter — plus 'port' and 'username' are left entirely unexplained.

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 verb and resource: 'Open an SSH session to a router'. It is clear what the tool does, but does not distinguish itself from the sibling 'reconnect', which is a near-neighbor an agent could easily confuse with this one.

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 gives operational guidance for the password parameter (leave empty to trigger a prompt), but says nothing about when to use this versus 'reconnect', 'discover_routers', or whether a session must be opened before 'run_command'. Usage is implied rather than stated.

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