execute_hscript

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

With no annotations provided, the description carries the full burden of explaining behavior. It only states that stdout/stderr are returned, but fails to disclose that executing arbitrary HScript commands can modify the scene, have side effects, or require specific permissions. This is a significant transparency gap for a command-execution tool.

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 a single, clear sentence that directly communicates the tool's purpose with no redundant words. It is appropriately concise and front-loaded, fully earning its place.

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, no output schema, and the tool's potential for arbitrary code execution, the description is incomplete. It does not explain return format (beyond mentioning stdout/stderr), error behavior, side effects, or when to use this tool relative to the numerous sibling tools. The description is minimally viable but leaves out critical context for safe and correct usage.

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 schema has one parameter 'command' with 0% description coverage, so the description must compensate. It does not elaborate on what constitutes a valid HScript command, how formatting should be handled, or any constraints. The parameter name is self-explanatory, but the description adds no semantic value beyond the schema.

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 'Execute an HScript command and return stdout/stderr' clearly identifies the action (execute) and resource (HScript command) with a specific outcome. However, it does not differentiate itself from the sibling tool 'execute_houdini_code', which likely has similar semantics, so it misses the full 5 for sibling distinction.

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 provides no guidance on when to use this tool versus alternatives like execute_houdini_code or evaluate_expression. There is no context on prerequisites, intended scenarios, or scenarios where another tool should be preferred.

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