blender_batch

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

Annotations are all false, so the description carries the burden of disclosing side effects. It does not state whether files are overwritten, whether a Blender session is required, or any limitations. The operations imply file writes and modifications, but no explicit behavioral disclosure is 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?

The description is appropriately concise: an intro, a three-item bullet list, a return format line, and a code example. It is well-structured and front-loads the main purpose, with no unnecessary verbosity.

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 10 parameters and three distinct operations, the description is too sparse. It lacks per-operation parameter mapping, prerequisites, and edge-case behavior. The standard return format and output schema existence do not compensate for the missing operational detail.

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?

With 0% schema coverage, the description must compensate. It explains 'pattern' defaulting to *.png and 'name_pattern' for export, but leaves unclear key parameters like width/height, source_format/target_format, and output_dir. The example demonstrates input_dir usage, but many params remain semantically opaque.

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 'Batch image and mesh export operations' and enumerates three specific operations (resize, convert, export), which defines a concrete scope. It differentiates from siblings like blender_export by focusing on batch and multi-type operations, though it doesn't explicitly contrast each mode.

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 explicit guidance on when to use this tool versus alternatives is given. The name implies batch use, and the operation list suggests scenarios, but there is no mention of exclusions or when to prefer a sibling like blender_export or script_execute.

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