run_accoreconsole_script

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

With no annotations, the description carries the full behavioral burden. It discloses the headless environment, optional input drawing, optional save path, and timeout, but omits whether scripts can modify the input drawing, what happens without save_as_dwg, how timeouts or failures are handled, and what side effects arbitrary script execution may have.

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 front-loaded with the purpose and then uses a compact Args list. There is no filler, and each sentence or argument line carries necessary meaning.

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?

An output schema exists, so return values need not be explained, and the parameters are well covered. However, for a code-execution tool with no annotations, the description is incomplete regarding when to select it over sibling tools and how its side effects and failure modes behave.

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%, but the Args section explains all five parameters, including the coupling between script_or_lisp and is_lisp, the optional open/save drawing paths, and the timeout meaning. This fully compensates for the bare schema titles.

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?

States a specific verb and resource: run batch AutoLISP or .scr scripts in AutoCAD 2027's headless AcCoreConsole. The batch/headless framing distinguishes it from in-process siblings such as eval_autolisp and send_command, even without naming them.

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 batch and headless AcCoreConsole framing implies its use case, but there is no explicit comparison to alternatives like eval_autolisp or send_command. It does not say when not to use this tool or what prerequisites are required.

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