import_folder

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

No annotations are provided, so the description carries the full burden. It states 'Import all files' but does not disclose what happens if the folder is empty, if files are unsupported, or whether this operation is destructive. No mention of error handling, side effects, or required 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?

The description is a single sentence of five words, which is extremely concise. However, for a tool with two parameters and no annotations, it may be too sparse to be fully helpful. It is not wasteful, but under-specification slightly reduces effectiveness.

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 the complexity (two parameters, no output schema, no annotations, and many sibling tools including 'import_footage'), the description is incomplete. It does not specify whether folders are imported as collections or individually, what happens to existing project structure, or how errors are handled. The agent lacks sufficient context to use the tool reliably.

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 description coverage is 100%, so parameters are already documented. The description adds 'all files' which clarifies the scope but does not provide additional meaning beyond the schema. Baseline 3 is appropriate as the schema does the heavy lifting and the description offers marginal value.

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 verb 'import' and the resource 'all files from a folder'. It distinguishes from sibling tools like 'import_footage' which imports specific footage files, and other unrelated tools. The purpose is specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives such as 'import_footage' or 'replace_footage'. The description does not specify prerequisites, potential conflicts, or scenarios where another tool would be more appropriate.

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