surgical_read

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

No annotations provided, so description must cover behavior. It states 'Read only' implying no modifications, but lacks details on permissions, rate limits, or what constitutes 'exact code lines'. Could mention it does not traverse dependencies.

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 concise sentence with an example. Front-loaded with action and object. No wasted words.

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?

Tool is simple (single required parameter). Has output schema (not shown). Description covers purpose and parameter format. Could optionally mention return format (e.g., 'returns code lines as string'), but output schema likely handles that.

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% coverage, but description adds meaning: 'symbol_id (e.g. 'src/app.py::main')' explains the format and purpose. This compensates for the schema gaps.

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 clearly states it reads exact code lines for a specific symbol_id, using verb 'Read' and specific resource 'symbol_id'. Distinguishes from sibling tools like apply_surgical_patch (which modifies) and semantic_search (which searches).

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 phrase 'Read only the exact code lines' implies a narrow, specific read operation. While it doesn't explicitly state when not to use or mention alternatives, the context suggests it is for precise symbol lookups, not broad searches. Sibling tools offer different functionalities.

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