serial_set_rts

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 mentions the tool sets RTS state and hints at a use case for bootloader entry, but lacks details on behavioral traits such as required permissions, side effects (e.g., device reset), rate limits, or error handling. This leaves gaps in understanding how the tool behaves beyond its basic function.

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 concise and front-loaded, consisting of two sentences that directly state the tool's function and a key use case without unnecessary details. Every sentence adds value, making it efficient and well-structured.

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 moderate complexity (hardware control), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and a use case but lacks details on behavioral aspects, error conditions, or output expectations, leaving room for improvement in completeness for safe and effective use.

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%, with clear descriptions for both parameters ('connection_id' and 'state'), so the description does not need to add parameter details. The description does not provide additional semantic context beyond what the schema offers, such as explaining the implications of RTS state changes, aligning with the baseline score when schema coverage is high.

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 action ('Set RTS line state') and the resource ('RTS line'), making the purpose understandable. However, it does not explicitly differentiate from sibling tools like 'serial_set_dtr', which likely sets a different control line, though the mention of 'bootloader entry on ESP32/STM32' hints at a specific use case.

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 'bootloader entry on ESP32/STM32', suggesting a specific context, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., 'serial_set_dtr' for DTR line control) or any prerequisites beyond the implied connection setup. No exclusions or clear alternatives are stated.

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