pwntools_tube_recvline

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

Annotations provide readOnlyHint, idempotentHint, and destructiveHint, indicating safe read operation. Description adds that it receives a line, but doesn't detail line termination expectations, timeout behavior, or what happens if no newline received. With annotations covering safety, the description provides minimal extra context.

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?

One concise sentence front-loads the key action and resource. Every word is necessary; no 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?

Given the tool's simplicity and presence of an output schema (assumed), the description is functionally sufficient but lacks details like return value type, line delimiter, or error conditions. With sibling tools providing context, some implicit understanding exists, but more completeness would help.

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 already describes all three parameters (nbytes, timeout, tube_id) with descriptions. The tool description adds nothing beyond the schema, so baseline 3 is appropriate given schema coverage is fully documented.

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 'Receive a single line from an active tube' clearly states the action (receive) and resource (single line from tube), distinguishing it from siblings like pwntools_tube_recv (bytes) and pwntools_tube_recvuntil (until pattern). It is specific and unambiguous.

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?

No explicit guidance on when to use vs. alternatives (e.g., recv, recvuntil). The purpose implies use for line-oriented input, but missing exclusions or context about line termination, blocking behavior, or tube prerequisites.

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