scan_directory

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

The description presents a read-only scanning operation, but annotations include destructiveHint=true, creating a contradiction. The description does not address or explain this destructive annotation, which could mislead an agent.

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?

Description is concise (5 sentences) with front-loaded purpose. Every sentence adds value: purpose, output format, clarification of findings, usage guidelines, and sibling reference. 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?

For a tool with 2 parameters and no output schema, the description provides comprehensive context: purpose, return structure, legal caveats, related tool (get_law_reference), and usage guidance. Covers all necessary aspects.

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 coverage is 100% with parameter descriptions. The description adds context: default pattern '*.java', examples, and mentions detectors target Java/Kotlin-style source, enhancing understanding beyond the 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?

The description clearly states the tool's function: scanning a directory tree for Korean compliance risks across specific acts. It specifies the output format and distinguishes from sibling tool scan_file for single files.

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 tells when to use this tool ('for a whole project or folder') and when to use the alternative ('use scan_file for a single file'). No ambiguity.

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