exec_python

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

With no annotations provided, the description carries the burden but only discloses two traits: helpers are pre-bound and top-level await is allowed. It does not state that running arbitrary code can mutate state, that errors are surfaced in a particular way, or how results are returned. For an execution tool, more behavioral disclosure (e.g., that this runs in the live daemon and can have real side effects) would be warranted.

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?

Two sentences, zero waste. Every clause earns its place: the execution environment, the helper binding, await support, and a concrete usage example. Front-loaded with the core action first.

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?

The tool is complex (arbitrary code execution) with no output schema and no annotations, making it a higher-burden case. The description explains what it does and when to use it, but falls short on what the agent should expect regarding return values, error handling, or side effects. It's adequate for a generic escape hatch but could better set expectations for a complex 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?

Schema description coverage is at 100%, so the schema fully documents the single 'code' parameter. The description adds context about what the code runs in (helpers pre-bound, await allowed), which adds some value, but the baseline 3 is appropriate since the schema already covers the parameter's meaning.

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 it runs arbitrary Python in the daemon namespace with helpers pre-bound and top-level await. The verb+resource ('run arbitrary Python') is specific and distinguishes this from the many sibling navigation/scraping tools via its generic escape-hatch nature, though it doesn't explicitly name a sibling 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 provides a clear when-to-use signal: 'Use when no single tool fits' and gives an example (multi-step flows in one round trip). This is strong contextual guidance against its many specialized siblings, though it doesn't enumerate explicit when-not-to-use cases or name alternatives.

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