Stop a logcat stream

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

Annotations cover readOnly/idempotent/non-destructive, and the description adds real behavioral value beyond them: it discloses that buffered-but-unread output up to max_bytes is returned here and that excess is discarded and reported. Note a mild tension between a 'terminate/forget' operation and readOnlyHint=true, but for an ephemeral session-scoped stream this is defensible rather than a hard contradiction.

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 tight sentences, front-loaded with the primary action (terminate + forget) followed by the return/discard behavior. Every clause carries information; no filler.

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 no output schema, the description carries the burden of explaining returns and does so (buffered output up to max_bytes, overflow discarded and reported). It omits error behavior for an unknown/already-stopped stream_id, though idempotentHint partially covers that.

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 coverage is 100% (baseline 3), and the description adds meaning beyond the schema by explaining how max_bytes governs the returned buffered output and that overflow is discarded and reported. It also implicitly clarifies that stream_id is consumed and invalidated after the call.

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?

States a specific verb and resource: 'Terminate a logcat stream and forget its stream_id.' This clearly separates it from start_logcat_stream and read_logcat_stream, though the differentiation with read_logcat_stream (read without terminating) is only implied rather than named.

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?

Usage is implied by 'forget its stream_id' (call this as final cleanup), but there is no explicit when-to-use or when-not-to-use guidance relative to read_logcat_stream, which is the natural alternative for retrieving buffered output without terminating.

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