debug_set_breakpoints

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

Annotations already idempotentHint=true, description adds detail: replaces previous breakpoints, returns verification per breakpoint, zero-based lines. No contradiction.

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?

Two sentences with key information front-loaded: purpose, return, important notes. 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?

No output schema, but description states return format. Covers all essential aspects: what, how, important constraints. Complete for a simple tool.

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?

Schema covers both params well; description adds crucial detail: zero-based, [] clears breakpoints, matching other 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?

Clear verb+resource: 'Set breakpoints in a GDScript file' with replacement behavior. Distinct from siblings like debug_pause or debug_inspect.

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?

Provides context: set before running, then use stack trace/inspect. Lacks explicit when-not-to-use, but clear usage flow.

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