reconnect

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

The description clearly states the tool 'Disconnects and reconnects' and returns the current VPN status. With no annotations, this effectively communicates the mutation and outcome, though it lacks details on failure 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?

The description is concise with a clear structure: brief intro, Args list with examples, and Returns. It is well-organized and front-loaded, though the Args section could be more succinct.

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?

Given the presence of an output schema, the description properly notes the return value. It covers the core behavior and parameters, but lacks details on error handling or constraints, which are not critical for a simple reconnect action.

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 description provides concrete examples for each parameter (e.g., 'se', 'got', 'se-got-wg-004'), adding critical format context beyond the input schema's type-only definitions. This helps an agent use the parameters correctly despite 0% schema coverage.

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 clearly states 'Reconnect to Mullvad VPN' and explains that it disconnects and reconnects optionally to a new relay location. This directly distinguishes it from sibling tools like 'connect' and 'disconnect' which handle individual actions.

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 implies when to use this tool (to reconnect with optional location change) but does not explicitly contrast with alternatives like 'connect' or 'disconnect'. No guidance on when not to use it is provided.

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