Read File Range

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that it reads a bounded line range, which is the key behavioral trait. However, it does not disclose edge cases like what happens if startLine > endLine or if the file doesn't exist.

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?

Single clear sentence that efficiently conveys the tool's purpose with no extraneous words. Front-loaded with the core action.

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?

The description is minimal and leaves out usage guidelines and parameter details. Given that there is an output schema (reducing need to explain return values) and 4 required parameters, the description could provide more context about the range parameters or file path format.

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 has 0% description coverage for parameters. The description implies that 'startLine' and 'endLine' define the range via 'bounded line range', but provides no additional meaning for 'projectPath' or 'file'. Baseline 3 is appropriate as it adds partial value.

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?

Description explicitly states 'Read a bounded line range from one text file inside a project.' It specifies the verb 'read' and the precise resource (bounded line range, one text file), distinguishing it from siblings like 'code.read' (reads whole file) and 'code.search' (searches content).

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 on when to use this tool versus alternatives. For example, it does not mention that reading the entire file should use 'code.read', or that searching across files should use 'code.search'. Missing context for tool selection.

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