engine_image_dir_add

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

With no annotations provided, the description carries the full behavioral burden. It discloses a key constraint (parent must exist) and implies non-recursive creation. However, it does not mention what happens if the folder already exists, whether the operation is idempotent, or any permission requirements.

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?

Two short sentences with no filler. The purpose is front-loaded and the critical precondition immediately follows. Every word earns its place.

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 single-parameter tool with no output schema and no annotations, the description covers purpose and the main precondition. It is minimally viable, but an agent might also need to know success/error behavior and the tool's relationship to sibling directory tools for full confidence.

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?

The schema has 0% description coverage, so the description must clarify the 'path' parameter. It does add meaning by stating that 'path is the whole new folder' and that its parent must exist. However, it omits format details (absolute vs relative) and lacks examples, so it only partially compensates for the schema gap.

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 verb ('Create') and resource ('images folder'), which clearly identifies the tool's operation. It is distinguishable from sibling dir tools like engine_static_dir_add by the explicit 'images' qualifier, though it does not name the sibling it differs from.

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?

The description provides a clear precondition ('parent must exist') that guides when and how to use the tool. However, it does not explicitly state when to use this tool over alternatives, such as engine_static_dir_add, nor does it mention any exclusion cases beyond the parent requirement.

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