Start Device Command Job

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

Annotations declare readOnlyHint=false (mutation) and idempotentHint=false, but the description adds real value: it explains 'detached' behavior, the immediate job-id return, the default user-session environment, and the >15s duration threshold. It doesn't mention how long jobs persist (though timeout param covers it) or rate limits, but this is solid additional context beyond annotations.

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 tightly packed sentences: first states what the tool does, second states when to use it. Zero filler, front-loaded action.

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?

Complete for a job-starting tool with no output schema: it explains the job-id return, the detachment, the environment, and the use-case threshold. Missing a note on how to check job status (sailfish_device_command_status) or cancel, but that's a routing detail rather than a correctness gap.

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 100%, so all four parameters are documented in the schema with rich detail (USB alias semantics, argv-not-shell, lifetime, runuser). The description adds only the 'user-session environment' framing, which is useful but doesn't go beyond what the schema provides for individual parameters. Baseline 3 for high coverage.

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?

States a specific verb (start), a specific resource (detached SSH command job), and its key mechanism (returns a job id). Unambiguously distinguished from siblings like sailfish_device_user_session_command and sailfish_device_command_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?

Explicitly names use cases (GDB, tracing) and a threshold (>15s), which is clear routing guidance. It doesn't explicitly name the alternative sibling (e.g., a non-detached synchronous command tool), so it's a 4 rather than a 5.

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