dbgprobe.rtt.start

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

With no annotations provided, the description carries full burden. It mentions connecting to a telnet port and buffering output, but lacks details about idempotency, whether it can be called multiple times, error conditions, or side effects like blocking behavior. Basic transparency but incomplete.

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 consists of two concise sentences. The first sentence front-loads the purpose, and the second adds the optional parameter detail. No fluff or redundant information.

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's simplicity (start RTT), the description is mostly complete: it explains the action, connection method, and optional address. However, it lacks mention of return values (no output schema) or prerequisites like verifying the session is active or that RTT is enabled in firmware. Could also hint at post-conditions like using rtt.read.

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 description coverage is 100%, providing detailed parameter info (e.g., address accepts integer or hex string). The tool description adds minimal extra context beyond 'Optional address hint'. For session_id, the schema description is minimal; the tool description does not elaborate. Baseline 3 is appropriate as schema does most of the work.

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 verb 'Start RTT' and the resource 'connected session', and explains the action: connects to JLinkGDBServer RTT telnet port and buffers target output (channel 0). This distinguishes it from sibling tools like dbgprobe.rtt.stop, read, write, and status.

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 provides context that a connected session is needed (session_id from dbgprobe.connect) but does not explicitly state when to use this tool versus alternatives, when not to use it, or any prerequisites beyond the session. Sibling tools are not referenced for guidance.

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