read_file_lines

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, setting a safe-read baseline. The description adds valuable context beyond annotations: the output format ('like cat -n') and the permission requirement (allow_file_read). No contradictions with annotations.

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?

Three sentences, each serving a distinct purpose: stating the core function, providing usage differentiation, and noting a prerequisite. No fluff, and the main action is front-loaded in the first sentence.

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?

With no output schema, the description compensates by stating the return format ('cat -n'). It covers purpose, usage guidance, and a prerequisite, making it reasonably complete for a simple file read tool. Edge cases like file-not-found are not mentioned, but these are not essential given the low complexity.

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 descriptions cover all three parameters (path, limit, offset) with types, defaults, ranges, and meaning, so schema coverage is 100%. The description only restates the offset/limit navigation concept, adding no new semantics beyond the schema. Baseline 3 applies.

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 a file with line numbers and supports offset/limit navigation, explicitly distinguishing it from read_file by prescribing use when line numbers or specific sections are needed. This is a specific verb+resource+scope that differentiates it from the sibling read_file tool.

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?

Provides clear when-to-use guidance: 'Use this instead of read_file when you need line numbers or want to read a specific section.' It also notes the require allow_file_read prerequisite. However, it does not mention alternatives like tail_file or when-not conditions, so it is not exhaustive but still practical.

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