serial_wait_for

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

Annotations provide readOnlyHint=false, destructiveHint=false, openWorldHint=true. The description goes beyond by detailing blocking behavior, timeout, and the ability to send respond/respond_hex immediately upon pattern match with sub-millisecond granularity. This is critical behavioral context not captured in 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?

The description is well-structured with a clear initial sentence, an important note about respond behavior, a list of use cases, and examples. While slightly lengthy, all content adds value and is organized. Could be trimmed slightly but effective.

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 no output schema, the description does not specify what the tool returns (likely the matched string or a boolean). However, it covers all other aspects: behavior, parameters, and examples of output usage. A minor gap in return value documentation.

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 coverage is 0% (no descriptions in schema), but the tool description includes a comprehensive 'Args' section explaining each parameter (pattern, timeout, session_id, encoding, respond, respond_hex) with examples. This fully compensates for the lack of 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?

The description clearly states 'Wait for a specific pattern to appear in the serial output' and provides multiple examples. The verb 'wait' and resource 'serial output' are specific, and it distinguishes from siblings like serial_read or serial_command by focusing on blocking until pattern match.

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 explains usage scenarios: waiting for boot messages, login prompts, etc. It implies when not to use (e.g., if you just want to read data without blocking, use serial_read). However, it does not explicitly exclude alternatives or mention prerequisites.

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