system.execute_python

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It mentions the disabled state but does not disclose security implications, side effects, permissions, or return behavior. For a tool that executes arbitrary code, critical safety information is missing.

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 a single concise sentence with no wasted words. However, it omits important details that would justify additional length, such as security caveats or return value. Still, for conciseness, it scores high.

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 single parameter, no output schema, and no annotations, the description should provide enough context for safe and correct use. It lacks information on execution results, error handling, and potential impact on Blender state, making it incomplete for a powerful and potentially dangerous tool.

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 input schema has one parameter 'code' with a description 'Python source to exec' that adds no semantic meaning beyond the parameter name. Schema description coverage is 0%, and the tool description does not compensate by explaining acceptable code formats, limitations, or execution context.

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 action ('Run Python inside Blender') and the resource (Python inside Blender). It also includes a constraint ('disabled unless explicitly enabled') which adds context. The purpose is specific and distinct from sibling tools like script.run_file, though not explicitly differentiated.

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 on when to use this tool versus alternatives such as script.run_file or other execution methods. The only hint is that it is 'disabled unless explicitly enabled,' implying it requires special permission, but no explicit when-to-use or when-not-to-use instructions are given.

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