batch_process_directory

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

Annotations only provide a title, so the description carries the full behavioral burden. It discloses that script_code is applied to .blend files, but it does not mention whether files are modified, saved, or whether the operation is destructive or reversible.

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 concise sentence with no filler and the main operation is front-loaded. It is efficient, though the brevity omits meaningful details that would improve its usefulness.

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 that executes arbitrary code across multiple files, with no annotations and no output schema, this description is too minimal. It does not explain return values, side effects, failure behavior, or how script_code is interpreted.

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 0%, so the description must compensate. It mentions directory and script_code by role but does not explain the expected format of script_code, whether it is optional given its default, or how the directory path should be specified.

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 states a specific action and scope: process all .blend files in a directory using script_code. It is mostly clear, but 'process' is generic and it does not explicitly distinguish itself from siblings like execute_blender_code or batch_execute_on_objects.

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?

There is no guidance on when to choose this tool over alternatives, no prerequisites, and no exclusions. The description implies batch usage but does not state when a user should prefer it over related batch or execution tools.

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