logging

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, so the safety profile is partly covered. The description adds the channel-to-parameter mapping, but says nothing about whether start blocks, whether logs persist across sessions, what get returns, or that clear discards buffered entries — all relevant for a stateful multi-action 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?

A single dense line that front-loads the purpose, then presents actions and the channel/parameter rules compactly with no filler. Every clause carries information; nothing is redundant with surrounding prose.

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?

With 12 parameters, four mutating/side-effecting actions, and no output schema, the definition should say more about what get returns (entries with indices, per since_index) and what clear/stop do to ongoing capture. It covers the invocation surface but leaves the result and state-management behavior to inference.

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%, so the baseline is 3. The description's channel-conditioned parameter grouping (port/baudrate for uart, command/args/file for rtt/swo) largely echoes what the schema property descriptions already say, adding little beyond orientation.

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 concrete verb and resource ('Firmware log capture over a channel') and then enumerates the four operations with their argument shapes, so an agent immediately knows this is a log-capture tool rather than a config or state tool. It does not explicitly contrast itself with nearby siblings such as setup_swo or capture_state, which keeps it from a 5.

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 action grammar (start/stop/get/clear) implies the lifecycle, and the note that rtt/swo take command/args or file while uart takes port/baudrate hints at channel-dependent usage. However, there is no explicit statement of when to choose this tool over setup_swo, capture_state, or session_diagnostics, nor any prerequisites or exclusions.

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