system-execute_python

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

With no annotations, the description takes on the full burden of behavior. It discloses that stdout is captured and that a 'result' variable can be returned, which is essential for agent expectations. However, it does not mention error handling, side effects, or security implications, though these might be inherent to a code execution 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 extremely concise at two clauses, avoiding any filler. It front-loads the action and immediately states the output contract, earning every word.

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 a generic code execution tool, the description covers the essential inputs (code) and outputs (stdout, result). It does not explain use cases, but the tool is self-explanatory given its simplicity. The lack of an output schema means the description must convey return info, which it does. Missing error handling details slightly reduce completeness.

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 coverage is reported at 0%, meaning the description contributes minimal parameter guidance. The schema's property title itself describes the 'code' parameter, but the overall description does not add semantic details beyond mentioning the result variable. Given the schema already provides a useful title, this meets the baseline.

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 the tool runs Python inside Blender, with a specific verb ('Run') and resource ('Python inside Blender'). It also distinguishes from siblings like script-run_file (which runs an external file) by implying arbitrary inline code execution. The output behavior is explicitly mentioned, making the purpose unambiguous.

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 implies usage for arbitrary Python execution but does not explicitly state when to prefer this over alternatives like script-run_file or script-reload. No exclusions are given, but the lack of explicit context or alternatives keeps this at a basic level.

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