roku_debug_breakpoints_remove_all

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

No annotations are present, so the description must disclose behavioral consequences, but it only restates the action. It does not mention that removal is irreversible, that it affects breakpoints across the current debug session, or any side effects, leaving the agent to infer impact.

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 one short, grammatically complete sentence with no filler and no redundant detail. It is front-loaded and appropriately sized for a zero-argument operation.

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 the tool's simplicity and the presence of an output schema, the one-line description covers the core invocation. However, it leaves out usage context and behavioral caveats, which are not compensated by annotations, so it is adequate but not complete.

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 has zero parameters and schema description coverage is effectively 100%, so the schema leaves nothing undocumented. The word 'all' adds slight scope information, and for a no-parameter tool a 4 is the appropriate baseline.

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 clear verb and resource: remove all breakpoints. It is unambiguous and the word 'all' implies a distinction from the singular remove sibling, but it never explicitly differentiates itself from related breakpoint tools or defines the scope, so it stops short of a top score.

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?

There is no guidance about when to choose this tool over roku_debug_breakpoints_remove or roku_debug_breakpoints_list, and no mention of prerequisites such as an active debug session. The intended use is only implied by the action itself.

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