run_python

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

With no annotations, the description fully carries the transparency burden. It discloses preloaded names, global state persistence, REPL-like expression evaluation, the need to assign to `result` in statement mode, document recomputation, and return value structure including traceback on failure.

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 well-structured and front-loaded with the core purpose. Every sentence adds value, the example is directly useful, and there is no redundant filler. It earns its length.

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 such a powerful and open-ended tool, the description covers execution semantics, state persistence, return values, and recomputation. The main gaps are the undocumented `document` parameter and lack of safety caveats for arbitrary code execution, but overall it is highly complete.

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 description thoroughly explains the primary `code` parameter through REPL semantics, the `result` variable, and a detailed example. However, the optional `document` parameter is never mentioned, and with 0% schema coverage this leaves a notable gap in understanding its purpose.

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 opens with 'Execute Python inside FreeCAD,' giving a specific verb, resource, and action. It further distinguishes itself as 'the escape hatch for anything the typed tools cannot do,' clearly separating it from sibling typed 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?

It states that this tool is the escape hatch for anything the typed tools cannot do, implying it should be used when typed tools are insufficient. While it doesn't explicitly say 'use typed tools first,' the context is clear enough for an agent to decide.

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