File skeleton (bodies elided)

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

With no annotations, the description carries the behavioral disclosure burden. It transparently states that bodies are replaced with ' … {line}' and that indentation is preserved, which are the key behavioral traits. It does not cover every edge case, but the core behavior is well disclosed.

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: the first defines the output, the second gives the use case and rationale. Both are information-dense with no filler.

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 simple single-parameter tool with no output schema, the description fully covers what it does, what the output looks like, when to use it, and why (token savings). It is complete for the tool's 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?

The schema has 0% coverage for the path parameter, but the description's context makes it obvious that 'path' refers to the file to analyze. A single, self-explanatory parameter does not require extensive elaboration.

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 defines the tool as producing a structural skeleton of a file: every declaration's signature with indentation preserved and bodies replaced by a placeholder. This specific transformation distinguishes it from siblings like read_lines or outline_file.

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?

The description gives an explicit when-to-use guideline: 'Use this before any full read of a file over ~300 lines.' It does not explicitly name alternative tools or exclusions, but the threshold and context are clear.

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