Execute Mel

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. For arbitrary code execution, it says nothing about sandboxing, permission requirements, error behavior on failure, or the risk of running unchecked commands; 'escape hatch' gestures at risk but discloses no actual behavior. The undo-chunking and timeout details live only in the schema, not the description.

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?

A single ten-word sentence that is front-loaded with the verb and resource and contains no filler. It is arguably too terse for an execution tool, but every word earns its place and nothing is padded.

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 described, and the schema fully covers parameters. What is missing is behavioral context for a powerful execution tool with zero annotations: safety posture, failure modes, and session targeting expectations are left entirely to inference.

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 100%, with each of the four parameters (cmd, undo, timeout_s, session_key) already documented in the schema including defaults and ranges. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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: 'Evaluate a MEL command inside Maya', which is unambiguous and tells the agent this executes MEL rather than Python. The parenthetical 'escape hatch' hints at its role versus the dedicated sibling tools, but it never names execute_python or any alternative explicitly, so sibling differentiation is only implied.

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 phrase 'escape hatch' implies this is a fallback for tasks no dedicated tool covers, which is useful implied guidance. However, there is no explicit statement of when to prefer it over execute_python, nor any exclusion or precondition for its use.

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