pyocd_target_reset

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

Since no annotations are provided, the description bears full burden. It discloses the default halt behavior, which is critical for a reset operation. It does not detail side effects or prerequisites, but for a simple boolean-parameter tool, this is sufficient.

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 two sentences with no extraneous words. Information is front-loaded: first sentence states the action, second clarifies default behavior.

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 tool with one boolean parameter and an output schema, the description covers the core action and default. It omits any mention of return values, but an output schema exists, so that's acceptable. It could mention when the target halts after reset.

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 100%, so the baseline is 3. The description includes the default behavior ('resets and halts') which maps to the 'halt_after' parameter default, but does not add new meaning beyond the 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 clearly states 'Reset the target MCU' with a specific verb and resource, and adds default behavior 'resets and halts at the entry point', distinguishing it from sibling tools like pyocd_target_halt or pyocd_target_resume.

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 when resetting is needed, but does not explicitly compare to alternatives or state when not to use. Given many sibling tools, more guidance on when to prefer this over sequences of other tools would be helpful.

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