Splashtop Force Disconnect

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that it interrupts in-progress work, which is valuable beyond the annotations. However, it does not cover idempotency (idempotentHint=true) or potential side effects.

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 extremely concise with two sentences, front-loading the key action and warnings. 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?

Given the destructive nature and zero parameter documentation, the description is insufficient. It does not explain return values (despite output schema existing) or provide enough context for safe use beyond 'use sparingly.'

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%, and the description provides no information about the parameters (device_uuid, os_family, request_id). The agent cannot infer what these parameters mean or how to use them correctly.

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 'Force-disconnect ALL active Splashtop sessions on a device' with a specific verb and resource. It distinguishes from sibling tools like splashtop_initiate_connection or splashtop_session_status by focusing on disconnection.

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 warns to 'use sparingly' and notes it 'interrupts any in-progress operator work,' implying when to use with caution. However, it does not explicitly state when not to use or provide alternative tools for non-forced disconnection.

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