execute_program

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does so effectively. It explains key behavioral traits: tool calls are dispatched to MCP servers, only stdout from print statements is returned (not intermediate results), and all tool functions require await. It doesn't cover potential limitations like execution timeouts or error handling, but provides substantial operational context.

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 efficiently structured with zero wasted sentences. It front-loads the core purpose, then explains behavioral constraints, followed by clear usage guidelines. Every sentence adds essential information about how the tool works and when to use it.

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 with no annotations, no output schema, and a single parameter, the description provides comprehensive context about the tool's behavior, constraints, and appropriate usage. It explains the execution model, output limitations, and programming requirements. The main gap is lack of information about return format or error conditions, but overall it's quite complete for this complexity level.

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 the schema already documents the single 'code' parameter. The description adds some context about how MCP tools are accessed within the code (namespaced names) and the requirement to use print() for output, but doesn't provide significant additional parameter semantics beyond what the schema indicates.

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's purpose with specific verbs ('execute a Python program') and resources ('with access to MCP tools as async functions'). It distinguishes this tool's unique capability of running multi-step scripts with tool integration from direct tool calls, even though there are no sibling tools to differentiate from.

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 explicit guidance on when to use this tool ('when a task involves 3+ tool calls, loops, filtering, aggregation, or conditional logic based on intermediate results') and when not to use it ('for single tool calls, call the tool directly'). It clearly defines the appropriate context and alternatives.

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