execute_maxscript

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

Annotations already mark this as potentially destructive and not read-only, so the description does not need to repeat that warning. It adds useful behavioral context beyond annotations: arbitrary code execution, result return, and the asOneUndo grouping behavior. It does not contradict the annotations.

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 core content is compact and front-loaded: purpose, usage condition, and undo behavior appear in two short sentences per language. The bilingual duplication doubles the length, but each language version is tight and free of fluff.

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 an arbitrary code execution tool, the description covers the essential selection and invocation context: what it does, when to use it, and the key undo option. Schema examples cover code format. It does not detail error handling or result serialization, but annotations mitigate the missing safety warning.

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 the baseline is 3. The description mentions asOneUndo, but this largely restates what the schema already says. It adds no meaningful semantic detail beyond the schemas for code and label.

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 a MAXScript snippet and return the result. It also positions itself as the 'universal escape hatch' for reaching any Max feature without a dedicated tool, which clearly distinguishes it from the many specialized sibling tools.

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 explicitly says to use this tool when there is no dedicated tool for the desired Max feature. It does not name alternatives like execute_python or explicitly list exclusions, but the core routing condition is clear and actionable.

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