Splashtop Install

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

Annotations already indicate destructiveHint: true and readOnlyHint: false. The description adds valuable behavioral context: the install runs asynchronously and the distinction between request_permission and per-session attended access. This goes beyond what annotations provide. However, it does not disclose potential side effects like system modifications or reboot requirements.

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?

Comprises two clear, front-loaded sentences with no filler. Efficiently conveys the core action and key nuances. Could be slightly improved by separating the asynchronous note into its own sentence or bullet for clarity, but overall well-structured.

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 has 6 parameters (2 required), a destructive nature, and many sibling tools, the description is incomplete. It fails to explain required parameters like os_family (valid values?), device_uuid format, and how organization_uuid or account_type affect behavior. The asynchronous nature and permission control are addressed, but overall coverage is sparse for such a complex tool.

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%, so the description must compensate. It only explains the request_permission parameter, clarifying its role in user prompting vs. attended access. Other parameters (device_uuid, os_family, organization_uuid, account_type, request_id) are left unexplained, leaving gaps for a tool with 6 parameters.

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?

Clearly states it installs the Splashtop RMM client on a device. The verb 'Install' and resource 'Splashtop RMM client' are specific. Among sibling tools like splashtop_uninstall and splashtop_device_status, this description unambiguously identifies the installation action.

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?

Provides some implicit guidance by mentioning asynchronous execution, the request_permission parameter, and the requirement of a Remote Control subscription. However, it does not explicitly state when to use this tool versus alternatives (e.g., when not to use it, or contrasts with other Splashtop operations). The usage context is implied but not fully elaborated.

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