read_node_file

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

No annotations provided, so description carries full burden. Describes read-only nature, bounded output, line range with truncation notice, and long line chunking. Lacks mention of error handling for missing files or permissions.

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?

Four well-structured sentences. Front-loaded with core functionality, then behavioral details, usage flow, and constraints. Every sentence adds value.

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?

Given 4 parameters and no output schema, the description covers return behavior (truncation, chunking) and usage context. Could mention output format (plain text) but is otherwise complete.

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 provides descriptions for all 4 parameters (100% coverage). The description adds context beyond schema: explains pack-relative path with example, and clarifies default and max values for max_chars, line_count, start_line.

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 uses specific verbs ('read a slice of one file') and resource ('custom-node pack'), and clearly distinguishes from siblings like write_node_file, apply_node_patch, and search_node_packs.

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?

Explicitly states when to use this tool: after search_node_packs to locate the line, before apply_node_patch or write_node_file to change it. Also specifies local-only requirement and path restriction.

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