execute_hscript

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing about side effects, whether the command can mutate or destroy scene state, required context, or error behavior. For an arbitrary command-execution tool this is a significant 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?

Front-loaded and brief with no wasted sentences. The 'Args:' block largely restates the parameter name already in the schema, but the overall size is appropriate.

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-command execution tool with no annotations, no output schema, and 0% parameter schema coverage, the description omits almost everything an agent needs: side effects, safety profile, return behavior, and execution context. It is substantially under-specified for the tool's risk level.

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% and the single parameter is undocumented in the schema, so the description must compensate. It adds only that the value is an HScript command string, which distinguishes it from Python code but gives no syntax, format, or examples. Minimal but non-zero added meaning.

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: 'Execute an HScript command in Houdini.' An agent knows what the tool does, and the HScript qualifier separates it from execute_python. However, it does not explicitly contrast itself with sibling command-execution tools, 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?

No when-to-use guidance, prerequisites, or alternatives are given. The description never explains when HScript execution is preferable to execute_python, run_shelf_tool, or evaluate_expression, nor any exclusion conditions.

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