rhino_run_python

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

Annotations are all false (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), so the description carries full responsibility for behavioral disclosure. It mentions available libraries (rhinoscriptsyntax, RhinoCommon, scriptcontext) but fails to mention that arbitrary code can mutate the scene, cause side effects, or that execution may raise exceptions or have no return value. For a code-execution tool, this is a significant gap in transparency.

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 two sentences with no filler: it leads with the core purpose, lists the available libraries, and closes with usage guidance. Every sentence earns its place, and the message is front-loaded for quick scanning.

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 having an output schema, the description does not hint at return values, error behavior, or execution constraints (e.g., timeouts). For an arbitrary code execution tool, an agent needs to know what to expect on success or failure, but the description offers no such context. Given the complexity and power of the tool, this is a notable incompleteness.

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 reported as 0% (despite the param having a description, the signal indicates low coverage), so the description must compensate. The description only repeats the library access already stated in the schema's parameter description; it adds no new meaning about the 'code' parameter, such as expected format, common patterns, or edge cases.

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 action ('Execute arbitrary Python code') and the resource ('inside Rhino'), and explicitly differentiates from specialized tools by positioning it for 'advanced operations not covered by other tools.' This gives an agent a precise understanding of the tool's scope and distinguishes it from the numerous sibling tools.

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 gives explicit guidance on when to use: 'Use this for advanced operations not covered by other tools.' This directly tells an agent to fall back on this tool when specialized tools are insufficient. It doesn't mention when not to use it, but the positive guidance is clear enough to route – the alternative is implied to be every other tool.

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