execute_python

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

Annotations provide destructiveHint=true, and the description adds valuable context: 'Dangerous patterns are blocked by default' and 'Confirm required.' This discloses safety mechanisms and the need for confirmation beyond the annotation, though it does not detail what constitutes 'dangerous patterns' or post-confirmation behavior.

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?

Three concise sentences, front-loaded with the core purpose, followed by usage and safety notes. No wasted words, every sentence earns its place.

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 execution tool, the description covers purpose, when to use, and safety. An output schema is present, so return value details are not needed. It could mention execution limitations or environment specifics, but overall it provides a solid context for an agent to decide and invoke correctly.

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 has 0% description coverage for parameters. The description implies the 'confirm' parameter via 'Confirm required' and the 'code' parameter is self-evident from the tool's name, but it does not explicitly document parameter usage or formats. This partially compensates but leaves room for more explicit parameter guidance.

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 'Execute Python code inside Blender' with a specific verb and resource. It distinguishes itself from the many dedicated sibling tools by explicitly framing itself as a fallback ('Use this only when no dedicated tool exists').

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?

Provides explicit usage guidance: 'Use this only when no dedicated tool exists for the operation.' This tells the agent exactly when to prefer this tool over alternatives. It also mentions 'Confirm required,' indicating a required confirmation step.

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