run_montecarlo

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

Discloses asynchronous execution and immediate job_id return, adding value beyond minimal annotations. No contradiction with annotations.

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?

Single sentence, front-loaded with verb and resource, zero waste. Perfectly concise.

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?

Covers purpose, async nature, and return value. No output schema, but description explains job_id. Could mention how to use job_id later (e.g., check_job), but not necessary.

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 coverage is 100%, so the schema already documents both parameters. Description adds slight context (source of config_id and default for max_parallel), but does not significantly enhance 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?

Clearly states the verb 'execute', the resource 'configured Monte Carlo analysis', and key details (asynchronously, returns job_id). Distinguishes from sibling tools like configure_montecarlo and run_sweep.

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?

Implies the tool requires prior configuration (previously configured), but does not explicitly list when to use vs. alternatives (e.g., run_sweep) or when not to use.

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