pyocd_rtt_stop

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

The description adds 'release resources' beyond the name, disclosing that the tool performs cleanup. With no annotations, this provides adequate transparency for a simple stop action. It does not describe edge cases like idempotency or error states, but 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 extremely concise: one short sentence that is front-loaded with the action. No wasted words.

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?

Given zero parameters and the presence of an output schema, the description is mostly complete. It could mention whether the operation is reversible or what the system state is after, but for a stop/cleanup tool, it is adequate.

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?

There are no parameters, so the description does not need to explain them. Baseline score of 4 is appropriate.

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 'Stop RTT and release resources,' providing a specific verb (stop) and resource (RTT). It distinguishes from siblings like pyocd_rtt_start (starts RTT) and pyocd_rtt_status (checks status).

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 implied (stop when done with RTT), but no explicit when-to-use or when-not-to-use guidance is given. No alternatives are mentioned, though the sibling set makes it clear this is for stopping.

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