execute_python

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

With no annotations provided, the description must disclose behavioral traits on its own. It does state that variables persist between executions, which is a key stateful behavior. However, it omits other critical aspects such as error handling, output format, sandboxing, timeouts, or potential side effects, making the behavior of arbitrary code execution largely opaque.

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 two sentences long, with the main action 'Execute Python code' front-loaded. Every word serves a purpose, and there is no redundant or tangential information.

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 tool that executes arbitrary code, this description is underspecified. It does not explain what 'output' includes (stdout, stderr, exceptions), nor does it address side effects, resource limits, or session behavior beyond persistence. Since there is no output schema, the description should have elaborated further, but it leaves major gaps.

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 100%, so both parameters (code and reset) are fully described in the schema. The description adds no additional parameter semantics, but per the rubric, the high schema coverage warrants a baseline score of 3.

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 identifies the tool's function: executing Python code and returning output. This specific verb+resource combination distinguishes it from sibling tools like list_variables and install_package, which serve different purposes.

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 when one needs to run Python code, but it provides no explicit guidance on when to use this tool vs. alternatives. It does not mention list_variables or install_package or any exclusion conditions, leaving the usage context somewhat implicit.

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