remove_connection

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's marginal job is to add context. 'Forget' usefully signals that the stored profile is removed, not just the socket closed — but it says nothing about whether active operations are terminated, whether a missing profile errors, or whether the effect is reversible.

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?

One short sentence, front-loaded with the action, with no filler. It is efficient but borders on under-specified rather than optimally concise.

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?

A state-changing tool on persistent configuration with one undocumented parameter and no output schema, yet the description covers neither the parameter's meaning nor error behavior for unknown names. The agent has to guess at the key details.

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?

There is one required parameter 'name' with 0% schema description coverage, and the description never mentions it or its format (profile name vs. host string). With full burden on the description for this gap, the single vague noun 'connection profile' does not compensate.

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 pair ('close and forget') and resource ('connection profile'), which is clear and differentiates it from add_connection and list_connections. It stops short of naming siblings, but the action is unambiguous.

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 indication of when to use this instead of, say, simply not using a connection, nor any precondition such as whether the connection must be idle. The agent must infer the appropriate context entirely.

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