serial_exec

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

With no annotations, the description carries the burden of behavioral disclosure. It accurately describes the core behavior (send, wait, read) and mentions the delay component. However, it does not disclose potential side effects like timeout behavior, Ctrl+C handling for resident commands, or the fact that command execution may have arbitrary effects. These are covered in the schema, but the description itself lacks this context.

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, consisting of two sentences with no fluff. The first sentence states the action, and the second explains the composite nature. It is front-loaded and every word adds value.

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 there is no output schema and the input schema covers all parameters well, the description doesn't need to explain parameter details. However, it is terse and does not place the tool in the broader context of sibling exec tools (e.g., ssh_shell_exec, adb_shell_exec) or mention important behavioral caveats like timeouts and interrupts that go beyond schema fields. It is sufficient for a simple tool but lacks some contextual depth.

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 the baseline is 3. The description adds minimal extra semantics by framing the delay parameter as part of the 'write + delay + read' sequence, which clarifies its purpose. However, it does not provide additional meaning beyond what the schema already gives for other 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?

The description clearly states the tool's function: 'Send a command to a serial shell session and wait for the output.' It identifies the specific resource (serial shell session), the action (send command), and the outcome (wait for output). It also differentiates itself from sibling tools like serial_write and serial_read by explicitly noting it combines write + delay + read.

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 by stating it combines write + delay + read in one call, suggesting it is for one-shot command execution. However, it does not explicitly state when to use this versus alternatives (e.g., serial_write/serial_read for streaming, or ssh_shell_exec for SSH sessions), nor does it mention any exclusions or prerequisites.

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