execute_code

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

No annotations are provided, so the description carries the full burden. It explains the return message, output, and screenshot, and even advises on screenshot behavior for non-visual changes. However, it does not explicitly warn about potential side effects of arbitrary code execution, such as destructive operations or persistence.

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-organized with an opening purpose statement, an Args section, and a Returns section. Each parameter explanation earns its place, especially the detailed note about include_screenshot. No redundant or verbose language is present.

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 the tool's complexity (arbitrary code execution), the description covers the core aspects: purpose, all parameters, and return values. It lacks any mention of prerequisites (e.g., requiring an open document) or a comparison to execute_code_async, which would make it more complete for an agent evaluating alternatives.

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. It clearly describes the 'code' parameter, explains 'include_screenshot' with a cost-saving rationale, and provides guidance on picking the right 'view_name' for the screenshot. This adds significant meaning beyond the bare 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 starts with 'Execute arbitrary Python code in FreeCAD', providing a specific verb and resource. It clearly states what the tool does, but it does not differentiate from the sibling tool execute_code_async, which is a closely related alternative.

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 no explicit guidance on when to use this tool versus execute_code_async or other siblings. It does provide advice on setting include_screenshot to false for analytical scripts, but that is parameter-level guidance, not tool-selection guidance.

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