read_rtt

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

With no annotations, the description carries the full burden. It states the tool is non-intrusive and does not need to halt the target, which is good. However, it does not disclose potential side effects (e.g., does reading clear the buffer?), error conditions, or authentication requirements.

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 well-structured with a concise overview and structured Args/Returns sections. Some redundancy exists (e.g., first sentence and last sentence both mention reading RTT content), but overall it is efficient.

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 annotations and 0% schema coverage, the description fairly covers prerequisites, parameters, and output. It lacks details on error handling or blocking behavior, but for a simple read tool, it is adequately 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?

The schema has 0% coverage, so the description must explain parameters. It provides default values and context: channel 0 is typical for log output, max_bytes limits read size. This adds significant meaning beyond the schema's bare titles.

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 it reads SEGGER RTT buffer content, explains what RTT is, and distinguishes it from the sibling write_rtt tool. The verb '读取' (read) and resource 'RTT 缓冲区内容' are specific.

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?

Describes a prerequisite (target firmware must include SEGGER RTT library), but does not explicitly state when to use this tool versus alternatives like read_memory or when not to use it. No exclusions or sibling comparisons are given.

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