keil_list_breakpoints

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

With no annotations supplied, the description carries the full burden; it does add one genuinely useful behavioral nuance by saying 'confirmed', implying pending/unapplied breakpoints are excluded, and scoping results to the current backend session. It says nothing about whether a debug session must be active or what happens when none are set.

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?

A single front-loaded sentence with no filler; every word (verb, qualifier, scope) earns its place. It is terse to the point of omitting useful routing context, but not verbose.

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?

An output schema exists and there are no parameters, so the description needn't explain return values; that keeps the bar low. However, for a session-dependent inspection tool with no annotations, it leaves out prerequisites (e.g. requiring an active debug session) and its relationship to the breakpoint-mutation siblings.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. It correctly avoids restating an 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?

States a specific verb+resource ('List confirmed breakpoints') and scopes it to 'this backend session', which an agent can distinguish from keil_set_breakpoint / keil_remove_breakpoint. It stops short of explicitly naming the sibling pair, so differentiation is implied rather than stated.

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 gives no when-to-use or when-not-to-use guidance and makes no reference to the sibling modify tools (keil_set_breakpoint, keil_remove_breakpoint) that an agent might otherwise reach for. Usage is only weakly implied by the verb 'List'.

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