evaluate_expression

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, and it says almost nothing. It does not disclose which expression languages work, whether evaluation has side effects on the scene, or any security/permission constraints beyond the bare 'return the result'.

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?

One efficient, front-loaded sentence with no filler. It is arguably under-specified rather than overly verbose, but structure-wise it wastes nothing.

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?

With an output schema present, return values needn't be explained, but the two undocumented parameters and lack of any language/context information leave the definition too thin for an agent to call this correctly alongside several script-execution siblings.

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 0%, so the description must compensate, and it does not. The 'language' parameter (defaulting to hscript) is never explained, and the accepted format or alternatives for 'expression' are left unspecified.

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+resource: 'Evaluate a Houdini expression and return the result.' An agent can tell it evaluates expressions rather than executing raw code, but the description does nothing to distinguish it from the close sibling execute_hscript.

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 at all. With execute_hscript, execute_houdini_code, and batch in the sibling set, the description never says when evaluating an expression is preferred over running a script.

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