lisp_execute_code

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

With no annotations provided, the description carries the full burden of behavioral disclosure. The words 'arbitrary' and 'directly' hint that execution is unrestricted and in-process, which implies destructive potential, but the description never discloses side effects, safety risk, error handling, or impact on the current drawing/session. For an arbitrary code execution tool, this is a significant transparency gap.

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 a single 8-word sentence with zero wasted words and the core action front-loaded immediately. It is admirably concise, though arguably under-sized for a tool with the risk profile of arbitrary code execution — every word earns its place, but more words were warranted.

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?

The output schema presumably covers return values, so that is not the gap. But for a high-complexity, high-risk tool with zero annotations, the description omits side-effect disclosure, error behavior, and selection context versus sibling tools. It conveys only the basic function, leaving an agent without enough context to call it safely or route to alternatives.

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%, so the description must compensate. It does clarify that the lone 'code' parameter holds AutoLISP code, naming the language the schema omits. However, it adds nothing about expected format (expression vs. full program, multiline handling, escaping) or how results map to the output schema, leaving the compensation incomplete.

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 and resource: 'Execute arbitrary AutoLISP code directly inside AutoCAD 2024+.' It clearly communicates the action, target, and version requirement. However, it does not differentiate from the closely overlapping sibling 'system_run_lisp', which likely also executes LISP routines, so it stops short of a 5.

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 about when to use this tool versus the highly relevant siblings 'system_run_lisp' and 'lisp_load_macro'. The description gives no selection criteria, no exclusions, and no context on when raw code execution is preferable over higher-level alternatives. It is simply a bare statement of capability.

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