htb_switch_vpn_server

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

No annotations provided. Description indicates a mutation ('switch') but does not disclose side effects (e.g., disconnection), authentication needs, rate limits, or error states. For a tool with no annotations, this is insufficient.

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?

Single sentence, front-loaded with action and result. No unnecessary words.

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 simple tool with one parameter and no output schema, description covers core usage and data source. However, missing behavioral context about side effects and error handling makes it incomplete.

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?

Single integer parameter vpn_id. Schema has 0% description coverage, but description adds meaning by stating it's a server ID from htb_vpn_servers. Lacks detail on valid range, format, or behavior for invalid IDs.

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?

Description clearly states the tool switches the HTB VPN server using a server ID from htb_vpn_servers. It uses specific verb 'switch' and resource 'assigned HTB VPN server', distinguishing it from sibling tools like htb_download_ovpn or htb_connection_status.

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?

Implicitly guides usage by referencing htb_vpn_servers for the server ID, but lacks explicit when-to-use and when-not-to-use, as well as prerequisites. No mention of alternatives among siblings.

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