connect_vps

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

The description details all automatic behaviors: checking/installing Python, installing libraries, copying files, testing MT5 connection, and handling unreachable SSH. It also notes the prerequisite that MT5 must already be installed and logged in.

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 well-organized with line breaks separating the overview from detailed steps. Every sentence is informative, though it is slightly long; still, it maintains clarity without redundancy.

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 tool's multi-step automation and conditional logic, the description covers prerequisites, success path, and failure handling (SSH unreachable). It also mentions the return value (found terminals).

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 parameter 'vps' is described as a friendly name from a list, with a reference to list_vps for available options. This adds valuable context beyond the schema's type and required flag.

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 verb 'configura' with resource 'VPS' and the explicit mention of first-time use clearly defines the tool's role. It distinguishes from siblings like check_vps_status or list_vps by specifying it's for initial setup of a VPS for mt5-remote-reader.

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 states explicitly that this tool should be called the first time a new VPS is used. It does not mention alternatives or when not to use, but the condition is clear and sufficient for the agent to decide.

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