read_capture

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

With no annotations provided, the description carries the full behavioral burden and does well: it discloses byte-offset pagination, truncation via escaping, UTF-8 boundary replacements, base64 losslessness, and scope restrictions. It does not cover all possible error conditions or return details, but the core behavioral traits are clearly communicated.

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 compact and front-loaded with the most important scoping information. Every sentence adds meaningful guidance, from what files are read to how to handle pagination and encoding, with no filler or 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 has four undocumented parameters, no annotations, and no output schema, the description is notably complete: it covers scope, encoding trade-offs, pagination hints, and recommended usage. It does not fully define the return structure or error cases, but the references to next_offset and lossless base64 provide enough context for an agent to invoke it correctly.

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 explain parameters, and it largely does: byte offsets clarify offset, UTF-8 versus base64 clarifies encoding, and 'read only needed excerpts' implies max_bytes usage. Path is partially clarified as being under RIGOL_DATA_DIR, but exact path semantics and next_offset (which appears only in prose, not the schema) could be more explicit.

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 tool reads generated data files under RIGOL_DATA_DIR, distinguishing it from screenshots and arbitrary files. It names a specific resource and action, and the contrast with siblings like screenshot and download_waveform makes its purpose 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?

The description provides practical usage boundaries: it is not for screenshots or arbitrary files, and it has no scope access. It also gives guidance on reading only needed excerpts and choosing base64 for lossless reads, though it does not explicitly name alternative sibling tools for scope-related data.

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