read_available

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that nothing is transmitted, that it waits up to read_timeout for first bytes, that it settles briefly to capture a full chunk, and that it returns data as both text and hex. This gives an agent a solid model of runtime behavior.

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?

Three sentences, tightly packed, with the core behavior front-loaded and no filler. Every sentence earns its place: what it does, when to use it, and how it behaves.

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?

The description is strong for a no-annotation tool: it covers purpose, use cases, timeout behavior, and return format, and an output schema exists to detail the response. The main gap is the unexplained connection parameter and the lack of explicit exclusions versus related tools, but these are minor and do not prevent correct invocation for the stated use cases.

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%, so the description must compensate. It adds real meaning for read_timeout ('Waits up to read_timeout for the first bytes'), but the connection parameter is never explained and is only represented by its name and default. This is a partial, not complete, semantic contribution.

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 opens with a specific verb and resource: 'Drain and return whatever the device has sent, without transmitting anything.' It clearly distinguishes this read-only drain operation from sibling send/query/expect tools, and gives concrete example uses like syslog, GPS, sensors, and binary replies after send_hex.

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 states explicit use cases: unsolicited/streaming output and grabbing a binary reply after send_hex. It does not explicitly list when not to use it or name alternatives like read_until_prompt, but the guidance is clear enough for an agent to select it appropriately.

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