gdb_list_breakpoints

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'structured data' indicating the output format, but fails to clarify what fields are returned, whether the operation is read-only, or if the debugger must be in a specific state.

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 single-sentence description is appropriately sized and front-loaded with the action verb. Every word serves a purpose, though the brevity leaves room for additional context given the lack of annotations or output schema.

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 simple listing tool with no parameters, the description provides the minimum viable information. However, given the absence of an output schema and annotations, it could be improved by specifying what breakpoint attributes (number, address, hit count, enabled status) are included in the 'structured data'.

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 with 100% schema description coverage (empty schema). The description correctly makes no parameter claims, meeting the baseline expectation for parameter-less tools.

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 the action ('List') and resource ('breakpoints'), distinguishing it from sibling CRUD tools like gdb_set_breakpoint and gdb_delete_breakpoint. The addition of 'structured data' hints at the return format, though specificity is limited without an output schema.

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?

No explicit guidance provided on when to use this tool versus alternatives (e.g., when to list all breakpoints vs. checking specific ones via gdb_get_status). The description lacks prerequisites or situational context.

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