micropython_reset

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 that the board is soft-reset (machine.reset()) and that reconnection is required afterwards, which is the key operational consequence. But it omits other material effects — that the running program and RAM state are lost, whether it is safe to call mid-execution, and how this differs behaviorally from a hard reset or interrupt.

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?

Two short lines: the first names the operation and its exact equivalent, the second front-loads the critical post-condition. Nothing is wasted and the most important fact (you must reconnect) is not buried.

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 zero-parameter tool with an output schema, the description covers what the agent needs to act: what it does and the state it leaves the connection in. The remaining gap is sibling differentiation, particularly against micropython_reset_and_capture, which the description never addresses.

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 no parameters, so there is no parameter semantics to document; the baseline of 4 applies. Nothing in the description conflicts with the empty schema.

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 states a specific verb ('soft reset') and resource ('MicroPython board') and even pins the semantics to machine.reset(), which removes ambiguity about what kind of reset this is. It does not, however, differentiate itself from the sibling micropython_reset_and_capture or micropython_interrupt, so the agent must infer which reset variant to pick.

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?

It gives one implicit usage signal — 'reconnection is required afterwards' — which tells the agent the connection will be lost and must be re-established. There is no explicit when-to-use guidance and no mention of alternatives such as reset_and_capture or interrupt, leaving the selection between reset siblings to inference.

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