set_trigger_serial

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the wire encoding (':'TRIGger:<PROTO>:<SUFFIX>' with booleans as 1/0) and the `extra` escape hatch, but says nothing about side effects, whether it overwrites existing trigger settings, or required instrument state.

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?

Front-loads purpose in the first line, then the encoding rule, then the per-protocol keyword reference. The long keyword dumps are justified given 0% schema coverage, though the list-heavy block is dense.

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?

An output schema exists, so return values need not be explained, and the description covers parameterization for every supported protocol plus an escape hatch with a manual reference. It omits only behavioral context (state changes, error handling) for a complex mutation tool.

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%, so the description must compensate, and it does: it maps each protocol to its documented keyword set and explains the fallback `extra={'KEYWORD': value}` mechanism. It is docked slightly because the `params` parameter is typed as a plain string in the schema while the description implies a structured/typed mapping, leaving the actual encoding of `params` ambiguous.

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 resource ('Serial-bus trigger') and enumerates the exact protocol families covered (RS232, IIC, SPI, CAN, LIN, FLEXray, IIS, M1553). This clearly distinguishes it from siblings like set_trigger_edge, set_trigger_pulse_width, and set_trigger_video without opening a schema.

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?

Usage is only implied by the protocol list; the description never states when to choose this over set_trigger_edge or the per-protocol configure_bus_* tools, nor any prerequisites such as needing the matching bus configured first. Adequate but with no explicit when/when-not guidance.

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