rhino_eval_expression

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

With no annotations present, the description carries the full burden of behavioral disclosure. It states that the tool evaluates an expression and returns a result, but it does not warn about potential side effects of arbitrary Python expressions, persistence of state, available RhinoScript modules, or risks of executing code. This is a notable gap for a code-evaluation 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 compact, front-loaded with the core action, and every sentence earns its place. The Args block is minimal and directly tied to the single parameter, with no filler or repetition.

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?

Despite being a single-parameter tool with an output schema, this is an arbitrary code execution tool with significant complexity and risk. The description lacks guidance on expression scope, available Rhino API aliases, side effects, or how to use it safely. It also fails to route the agent to related script-running tools, which leaves the definition incomplete for an AI agent.

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 only defines 'expression' as a string with 0% description coverage, so the description must add meaning. It does add 'valid Python expression string' and gives two concrete examples, which helps an agent construct a value. However, it does not elaborate on the evaluation context, supported modules, or whether RhinoScript functions are automatically available.

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 a specific verb and resource: evaluate a Python expression inside Rhino and return the result. It is not a tautology and the examples ('2 + 2', 'rs.WorldXYPlane()') clarify the intent, though it does not explicitly distinguish itself from sibling execution tools like rhino_execute_python.

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 guidance is provided about when to use this tool versus alternatives such as rhino_execute_python, rhino_run_python, or rhino_run_script_file. The description defines what the tool does but gives no exclusions, preconditions, or selection criteria, leaving the agent to infer appropriate usage.

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