Splashtop Session Status

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

Beyond annotations (readOnlyHint: true, destructiveHint: false), the description clarifies that can_start_new_session is simply a capacity indicator (current_sessions < max_sessions) and is independent of attended-access consent. This adds valuable behavioral context 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?

The description is a single, well-structured paragraph. It front-loads the core purpose and return fields, then adds clarifying behavioral notes. Every sentence adds value with no 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?

For a simple read-only status tool, the description covers the return fields and a key behavioral nuance (capacity vs. actual session start). Though parameters are undocumented, the tool is straightforward; the description is nearly complete for its complexity.

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 input schema has 3 parameters with 0% description coverage. The tool description does not explain any parameter meanings, defaults, or acceptable values. Given the schema description coverage is low (0%), the description fails to compensate, leaving the agent to infer from parameter names and types alone.

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 explicitly states 'List active Splashtop session capacity for a device' and names the returned fields (can_start_new_session, current_sessions, max_sessions). It distinguishes this tool from siblings like splashtop_get_attended_access and splashtop_device_status by focusing on capacity limits.

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 implies usage for checking session capacity but does not explicitly say when to use versus alternatives. It provides a caveat about attended access dependency, which guides the agent that additional checks may be needed, but lacks explicit when-not or alternative tool recommendations.

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