hac_impex_import

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses one side effect (successful scripts are auto-archived to the script library), but says nothing about failure behavior, that code execution is enabled by default, that strict validation is default, or what the import mutates in the instance.

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, front-loaded with the core action followed by the side-effect note. Every sentence earns its place, though the second sentence is the only added value.

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 9-parameter import tool with no annotations and no parameter documentation, the description is far too thin. The presence of an output schema relieves it of explaining return values, but the mutation, default options, and prerequisite context remain unexplained.

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% across 9 parameters, and the description mentions none of them. Parameters like file_path, script_content, validation_enum, enable_code_execution, and max_threads are entirely undocumented, leaving the description no compensating 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 states a specific verb (Imports) and resource (an ImpEx script into the SAP Commerce instance), which is clear and actionable. It does not name or differentiate against any sibling such as hac_groovy_execute or hac_library_get, but the purpose is unambiguous on its own.

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 use this tool versus alternatives, no prerequisites, and no exclusions. The only contextual statement is about archiving, which is a behavior rather than a usage condition.

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