serial_exec

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

No annotations are provided, so the description carries the full burden. It discloses concurrency hazards, buffer clearing via the 'clear' flag, timeout defaults, and that timeout type is annotated in output. However, it does not describe failure modes or output structure, which is a minor gap.

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 front-loaded with the core purpose, then adds a critical warning and a suggested alternative. It is somewhat lengthy but every sentence provides necessary operational detail, so it earns its place.

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's complexity (5 parameters, concurrency concerns, timeout behavior) and the lack of an output schema, the description covers essential usage, warnings, and alternatives. It stops short of specifying return data structure, but overall it is sufficiently complete for an agent to use effectively.

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 schema covers 100% of parameters with detailed descriptions, including maxDuration defaults and guidance, clear flag semantics, and delay purpose. The description adds the 'combines write+delay+read' context but does not materially extend parameter understanding beyond what the schema already provides, so the baseline of 3 applies.

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 it sends a command to a serial shell session and waits for output, combining write, delay, and read. It explicitly differentiates itself from sibling tools like serial_write, serial_read, and serial_send_ctrl by describing its composite nature.

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 explicit usage guidance: warns against concurrent calls on the same session, instructs to wait for previous commands, and recommends opening multiple sessions via serial_open for parallel execution. This gives clear when-to-use and when-not-to-use context.

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