refresh_debug_targets

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

With no annotations provided, the description carries full burden. It discloses the tool reloads a file and returns data, but lacks details on permissions needed, error handling, or side effects (e.g., whether it interrupts active debugging). It adds basic context but misses behavioral nuances for a file operation tool.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose and outcome with zero wasted words. It avoids unnecessary elaboration while being fully informative for its length.

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 has no parameters, an output schema exists, and complexity is low, the description is reasonably complete. It explains what the tool does and what it returns, though it could benefit from more behavioral context (e.g., error cases) since annotations are absent.

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 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's action and output without redundant parameter details, meeting the baseline for parameterless 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 specific action ('Reload launch.json') and the resource ('from current project'), with a distinct outcome ('return available debug configurations'). It differentiates from siblings like debug_start or debug_stop by focusing on configuration reloading rather than execution control.

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 implies usage when needing updated debug configurations, but provides no explicit guidance on when to use this tool versus alternatives like get_runtime_config or set_project. It lacks clear exclusions or prerequisites, leaving usage context to inference.

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