AxMeep_execute_code

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

With no annotations present, the description carries the full burden of behavioral disclosure. It fully discloses that execution is asynchronous on a remote Kubernetes job, returns a task_id with nothing simulated yet, has a typical 1-2 minute runtime with a 6-hour hard deadline, requires playground access, and rejects scripts that do not meet import/export requirements before submission at no cost.

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 compact yet information-dense: four sentences deliver async behavior, follow-up workflow, validation rules, cost implications, runtime, deadline, and access requirements. Every sentence adds value and the most important fact is front-loaded.

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 one parameter and an output schema that presumably documents the task_id return, the description is complete enough for an agent to invoke this tool correctly. It covers the async contract, follow-up calls, failure modes, timing expectations, and required access, leaving no material gap.

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 thoroughly, including the import and export requirements. The description reinforces these constraints but does not add meaning beyond the schema; the 'at no cost' detail is behavioral rather than parameter-specific, so the baseline 3 is appropriate.

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 opening line uses a specific verb and resource: 'Submit a Meep script for execution.' It also distinguishes itself from sibling execute_code tools by naming the Meep workflow and explicitly differentiating what happens now ('returns a task_id') versus later ('poll get_simulation_status, then call get_results').

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 gives explicit next-step guidance: poll get_simulation_status, then call get_results. It names the follow-up sibling tools and states the playground-access prerequisite. It does not explicitly say when to prefer this over AxMeep_generate_code, but the execution-vs-generation distinction is strongly implied.

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