Splashtop Set Attended Access

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

Annotations indicate destructiveHint=true and readOnlyHint=false, aligning with the description's caution about allowing unattended sessions. The description adds context about policy review and what the change entails, beyond what annotations provide.

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?

Two sentences with no fluff. First sentence states purpose, second provides caution. Efficient and front-loaded.

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?

The tool is simple with an output schema and annotations. The description covers the core effect and policy concern. It could mention the bulk sibling or the get sibling for completeness, but given the output schema, the agent can infer return values.

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%, yet the description only indirectly explains the required_attended_access parameter by mentioning end-user consent requirement. It does not explain device_uuid or request_id, so the description fails to compensate for missing schema descriptions.

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 verb (enable/disable) and the resource (end-user consent requirement for Splashtop sessions on a device). It distinguishes from sibling tools like splashtop_get_attended_access (get vs. set) and splashtop_set_bulk_attended_access (single device vs. bulk).

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 about reviewing organization policy before setting to false, implying when to use with caution. However, it does not explicitly state when to use this tool over alternatives (e.g., for checking current state use splashtop_get_attended_access).

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