lb_read_many_texts

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

Annotations already convey readOnlyHint=true and destructiveHint=false, and the description adds useful behavioral context: UTF-8 encoding, allowed-directory restrictions, and batched single-call reading. However, it does not disclose what happens if a path is missing, whether line_count/line_offset apply per file or across all files, or any error 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?

The description is a single front-loaded sentence with no filler or repetition. Every phrase adds meaningful information: what is read, the encoding, the directory restriction, and the batching behavior.

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?

This is a multi-file read tool with no output schema and 0% parameter descriptions, so the description needed to explain return shape, error handling for invalid paths or paths outside allowed directories, and how line_count/line_offset apply. The annotations cover the safety profile, but the operational details an agent needs for reliable invocation are missing.

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?

With schema description coverage at 0%, the description needed to explain file_paths, line_count, and line_offset. It only indirectly contextualizes file_paths as multiple UTF-8 text files; line_count and line_offset are left entirely to inference from their names, and their exact relationship to the batch read is unclear.

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 states a specific action (Read), resource (multiple UTF-8 text files), and constraints (inside configured allowed directories, in one call). This clearly distinguishes it from the singular lb_read_text sibling and leaves no ambiguity about the tool's core function.

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 establishes a clear use case: reading multiple UTF-8 text files in a single batch call, restricted to configured allowed directories. It does not explicitly name alternatives or say 'use this instead of lb_read_text', but the 'multiple' and 'in one call' phrasing gives an agent sufficient context to select it over the singular sibling.

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