stm32_reset_target

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

With no annotations provided, the description must carry full responsibility for behavioral disclosure. It only explains the parameters and their effects, but fails to mention side effects such as losing target state, potential disconnection, required debug probe connection, or error conditions. This is a significant gap for a mutating operation.

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 exceptionally concise, using two sentences to state the purpose and then clearly list the arguments. It is front-loaded with the main action, and every word adds value without redundancy.

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 simple tool with two parameters, the description covers the parameter semantics well. However, it omits important context such as prerequisites (e.g., a connected probe or active OpenOCD session), expected return behavior, and potential side effects. Given the absence of an output schema and annotations, more detail would be needed for full completeness.

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 is the sole source of parameter meaning. It thoroughly explains both parameters: hard_reset distinguishes hardware NRST pulse vs software reset, and port lists the valid values ('SWD', 'JTAG') and even maps to underlying command flags. 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 a specific verb ('Triggers') and resource ('target MCU reset'), and specifies the method ('via debug probe'). This distinguishes it from sibling tools like flashing, erasing, or reading memory, making its purpose unambiguous.

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 when to use the tool (to reset the target MCU), but it does not explicitly discuss alternatives or conditions when not to use it. No reference to other tools or scenarios is provided, leaving the choice to the agent's inference.

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