pyocd_breakpoint_list

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

The description correctly indicates a read-only listing operation. Although no annotations are provided, the description is straightforward and does not contradict any implicit safety expectations. It could be enhanced by noting that it lists breakpoints for the current session, but it remains 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 a single, complete sentence with no unnecessary words. It is perfectly concise and front-loaded.

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 no parameters and the existence of an output schema, the description is mostly complete. It could optionally clarify that it lists breakpoints for the currently connected target, but the current phrasing 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, and the schema coverage is 100%. The description does not need to add parameter details. Baseline score of 3 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 uses the specific verb 'List' and clearly identifies the resource as 'all active breakpoints'. This distinguishes it from sibling tools like pyocd_breakpoint_set (sets breakpoints) and pyocd_breakpoint_clear (clears breakpoints).

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 the tool is for inspecting current breakpoints. While no explicit alternatives or when-not-to-use guidance is given, the context of sibling tools and the simplicity of the operation make usage clear.

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