l2_batch_import_textures

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

Description contradicts schema by limiting formats to PNG/BMP while schema includes TGA/JPG. Also implies always creating new package without mentioning overwrite behavior or permissions. No annotations to compensate.

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?

Single sentence, concise, no filler. However, too brief given the tool's complexity.

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?

Missing details about return value, overwrite behavior, effect on existing packages, and contradicts supported formats. Incomplete for a 5-parameter tool with no output schema.

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% so baseline 3 is appropriate. Description does not add extra meaning beyond schema; it actually misrepresents supported formats.

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 verb 'import' and resource 'all PNG/BMP images from a directory into a new .utx package'. Distinct from singular import and extract siblings.

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 on when to use batch vs single import or extract. Does not differentiate from similar tools like l2_import_texture or l2_extract_all_textures.

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