execute_python

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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the agent knows arbitrary code may mutate the scene. The description adds useful environment context (Python 2.7 vs 3, pymxs compatibility) but does not discuss side effects such as undo behavior.

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 action and version caveat are front-loaded and compact, with no irrelevant detail. The bilingual duplication is slight overhead but is a reasonable accommodation rather than a meaningful completeness problem.

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 one-parameter arbitrary-code execution tool, the description covers what to pass, release-dependent availability, and pymxs version checking, and the destructive annotation covers risk. An explicit example or output/error behavior note would be nice but is not essential.

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?

The single parameter 'code' is 100% covered by the schema description, and the tool description does not add syntax, examples, or constraints beyond 'Python code to execute.' Baseline 3 is appropriate.

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 clear verb ('Execute') and resource ('the Python interpreter embedded in 3ds Max'), making the tool's function obvious. The 'if that release ships one' caveat and Python-specific framing distinguish it from the MaxScript execution sibling.

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 supplies a condition for use — only releases that ship Python — and a version prerequisite for pymxs scripts. It does not explicitly name an alternative like execute_maxscript, but the Python vs. MaxScript distinction is clear from context.

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