stm32_list_connected_probes

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

With no annotations, the description carries the behavioral burden. It clearly conveys a non-mutating discovery operation ('Scans') and enumerates the categories of hardware it will detect, including serial numbers and firmware versions for ST-LINK probes.

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 a single front-loaded sentence followed by a concise bulleted list. Every line adds a distinct category of detected hardware with no filler.

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?

For a parameterless discovery tool with an output schema, the description is largely complete: it states what is scanned and the main result categories. The only notable gap is the unresolved relationship with stm32_list_serial_ports.

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 tool takes zero parameters, so there is nothing for the description to clarify beyond the empty schema. The baseline for parameterless tools 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 uses a specific verb ('Scans') and names concrete resources: ST-LINK probes, DFU devices, J-Link adapters, and serial ports. However, it does not distinguish itself from the sibling stm32_list_serial_ports, which also covers serial/UART ports.

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 first line implies general use for inventorying connected STM32 hardware and probes, but there is no explicit when-to-use guidance or mention of alternatives. The overlap with stm32_list_serial_ports makes this ambiguity more noticeable.

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