serial_read

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

With no annotations, the description must disclose all behavioral traits. It only states 'read output', missing critical details like the default buffer clearing behavior (implied by the clear parameter default) and whether the operation is blocking or non-blocking. The parameter 'clear' is documented in the schema but not referenced in the description.

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 a single concise sentence with no wasted words. It is front-loaded with the key action and resource. However, it could be slightly more informative without becoming verbose.

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 output schema, the description should explain what the output looks like (e.g., plain text, streamed data) and any behavior like buffering. It does not mention that reading may clear the buffer or if multiple reads are possible. The tool's behavior is under-specified for an agent to use correctly without additional context.

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 input schema covers both parameters with descriptions (100% coverage), so the description need not add much. However, it adds no extra context beyond the schema, such as clarifying the relationship between session_id and serial_open or the meaning of the clear flag's default. Baseline 3 is appropriate.

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 the verb 'read' and the resource 'output from a serial shell session', making the primary purpose obvious. However, it does not differentiate from similar read tools for other shells like adb_shell_read or ssh_shell_read, but since the tool name includes 'serial', it is adequately 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?

No guidance is provided on when to use this tool versus alternatives such as serial_exec or similar read tools for other shells. No prerequisites, when-not-to-use, or contextual hints are given, leaving the agent to infer usage from the name alone.

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