fs_read_binary_chunk

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

The description discloses key behavioral details: base64 output and that a parameter value of 0 means unlimited reading, which is not evident from the schema. However, it omits error handling, edge cases, and how offsets are applied, leaving significant transparency gaps.

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 extremely brief, consisting of a fragment with three pieces of information. It is front-loaded and wastes no words, but the lack of structure and ambiguity make it borderline under-specified.

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?

For a tool with three parameters, no annotations, and an output schema, the description is too sparse. It does not explain offset behavior, file path expectations, or how this relates to sibling read tools, leaving significant gaps for the agent.

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?

Given 0% schema description coverage, the description adds meaning to at least one parameter: '0 unlimited' likely clarifies the max_bytes_to_read default. But bytes_to_skip and file_path are left implicit, relying on their names for understanding, so compensation is partial.

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 'Partial binary read, base64 output, 0 unlimited' indicates the tool reads part of a binary file and returns base64-encoded data, but it is phrased as a fragment rather than a complete sentence. It distinguishes from text reads by mentioning 'binary', but does not explicitly contrast with sibling read tools.

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 usage guidance is provided. The description does not mention when to use this tool over fs_read_full_text or fs_read_text_range, nor any prerequisites or exclusions.

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