read_rtt_log

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

There are no annotations, so the description carries the behavioral disclosure burden. It does note that only 'recent' log output is returned and that the tool depends on RTT running, which is useful. However, it does not explain what happens when RTT is not running, whether it blocks until output is available, how timeout_seconds affects behavior, or what the output looks like.

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 with no unnecessary words. It communicates the core action, the target resource, and an important precondition 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?

For a simple tool with two optional parameters, the description covers the basic purpose and condition, but gaps remain: no output format, no behavior when RTT is unavailable, and no parameter semantics. Since there are no annotations or output schema, the description should provide a bit more context to be fully complete.

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 0%, and the description provides no guidance about probe_id or timeout_seconds. The parameter names and defaults are self-explanatory to some degree, but the description does not compensate for the lack of schema descriptions or clarify units, semantics, or edge cases.

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 states a specific verb ('Read'), a specific resource ('SEGGER RTT log output from the target'), and a scope condition ('if RTT is running'). This clearly distinguishes it from sibling tools such as source_read, probe_read_memory, and probe_read_registers, which read different kinds of data.

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 gives a clear applicability condition: use this when you need recent SEGGER RTT log output and RTT is running. It does not explicitly discuss alternatives or when not to use it, but the condition and resource make the intended context reasonably clear.

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