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

Annotations already declare destructive=true, idempotent=false, openWorld=true, so the safety profile is known. The description adds genuinely new context beyond that: the batch nature, the cost implication of multiple test runs, and the need for prior approval. It stops short of describing what happens if part of the batch fails or whether queued runs can be cancelled.

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 short sentences with the operation stated first and the risk warning second. Nothing is redundant or buried.

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?

With no output schema, an agent still does not know what a successful call returns (batch identifier, list of run IDs) or how to track progress, which matters for a queued multi-run operation. The critical cost and confirmation risks are covered, but the result contract is not.

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% and the confirm parameter already carries an explicit 'set true only after the user approves this paid action' note, so the schema does the heavy lifting. The description's 'approve the batch first' reinforces confirm but adds no syntax or meaning beyond it, so the baseline of 3 applies.

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?

States a specific verb and resource: queue every simulation belonging to one assistant, which implicitly contrasts with the single-run sibling start_simulation_run. It is clear enough to distinguish from siblings, but it never names the batch-vs-single alternative explicitly.

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?

'Approve the batch first' implies the confirmation prerequisite, and 'can incur multiple test runs' warns of the scale of the action. However, there is no explicit when-not guidance, no statement of what preconditions must exist (e.g., simulations already created for that assistant), and no named alternative for launching a single run.

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