read_region

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

Discloses max 200 lines per call and returns numbered source lines. No contradictory annotations. Lacks details on error handling or side effects, but read operation is inherently safe.

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?

Two sentences, no extra words. Front-loaded with key action and constraint, followed by usage guidance. Every sentence earns its place.

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?

Covers purpose, constraints, return format, and usage guidance. Lacks mention of error cases or permissions, but acceptable given tool simplicity and no output schema.

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?

Adds value beyond schema by stating the 200-line limit and that output is numbered lines. Schema already describes parameters, so baseline is 3; description meaningfully enhances understanding.

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 specific line range from a file, with a 200-line limit. It differentiates from siblings by framing it as a way to read only needed code after using list_exports or file_outline.

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?

States to use after list_exports or file_outline to read only needed code, implying when to use it. Lacks explicit negative guidance (e.g., when not to use), but context is helpful.

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