debug_run

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

Discloses behavioral traits: runs in already open Godot editor, collects output, returns captured data, and implies blocking nature. Annotations are minimal (readOnlyHint=false, destructiveHint=false), so description adds valuable context without 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?

Concise, well-structured, and front-loaded with purpose. Every sentence adds value without redundancy.

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 complexity and lack of output schema, description adequately covers run behavior, output collection, breakpoints, and termination. Return values are summarized, but no structured format is provided.

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?

Parameter descriptions are fully covered in the input schema (100% coverage). The description does not add new meaning beyond schema; it provides context for usage (e.g., setting breakpoints) but not parameter-level details.

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?

Clearly states 'Run the project and collect what it prints', specifying verb and resource. Distinguishes from siblings by mentioning debug_set_breakpoints, debug_output, and debug_terminate for complementary actions.

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?

Explicitly describes when to use: 'edit, sync, run, and read the actual behaviour, without the developer pressing F5'. Provides guidance on setting breakpoints before calling and handling long-running games with alternative tools.

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