start_debug_session

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

No annotations provided. Description outlines main actions but does not disclose potential side effects (e.g., idempotency, blocking behavior, or what happens if already started). Still, the 'one-call' phrasing implies a safe initial action.

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, front-loaded with the key purpose 'One-call setup', minimal and efficient wording.

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 no parameters and no output schema, the description covers the setup steps and usage context well. Could briefly note if it blocks or returns immediately, but overall sufficient.

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?

Input schema has zero parameters with 100% coverage; description adds no parameter details as none exist. Baseline 4 for zero-parameter 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?

Description clearly states 'One-call setup: starts GDB server via SEGGER J-Link, connects RTT (if supported), waits for initial output.' Differentiates from siblings like gdb_server_start by being a combined setup.

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 says 'This is the recommended first tool to call' and provides conditional guidance: 'If no device is configured, use list_devices and set_device first.'

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