execute_script

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

With no annotations, the description carries the burden. It mentions 'escape hatch' implying risk, but does not explicitly detail behavioral traits like potential side effects, security implications, or execution limits. It is adequate but not comprehensive.

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 well-structured with bullet points for guidance and clear parameter descriptions. Every sentence adds value, and it is appropriately sized for the tool's complexity.

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?

Given no annotations and zero schema coverage, the description covers purpose, usage, and parameters thoroughly. It does not describe return values, but an output schema exists, so this is acceptable. Minor gap: no mention of side effects beyond the escape hatch label.

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 0%, so the description fully compensates by explaining that 'code' is Python code executed in the Isaac Sim context and 'cwd' is an optional working directory added to sys.path. This adds essential meaning beyond the schema's bare 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?

The description clearly states it is an 'escape hatch' to execute arbitrary Python code in Isaac Sim, and explicitly contrasts it with specific named tools, making its purpose highly distinct.

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?

It provides explicit when-to-use (operations no named tool covers) and when-not-to-use (prefer named tools for common tasks) guidance, and even suggests an alternative tool (reload_script) for persistent controllers.

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