scan_file

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

Description does not address the contradiction in annotations: readOnlyHint true but destructiveHint true. The description implies a read-only scan, but annotations suggest possible destructiveness. No explanation provided.

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, front-loaded with purpose and usage, no redundancy. 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?

Covers purpose, usage, and output shape (same as scan_directory). Missing discussion of permissions or error handling, but adequate for a simple tool. Slightly incomplete due to not addressing annotation contradiction.

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 already fully describes the path parameter with 100% coverage. Description adds only an example path, not substantial new meaning beyond schema.

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?

Clearly states it scans a single file for Korean compliance risks and returns JSON report. Distinguishes from sibling scan_directory by specifying single file vs whole project.

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 says use this for checking one file (e.g., current editor) and scan_directory for whole project. Also notes findings are not legal conclusions.

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