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

Annotations declare readOnlyHint=false and destructiveHint=false, so the write-but-non-destructive profile is already known. The description adds meaningful behavior beyond that: the call is asynchronous, returns a jobId immediately rather than results, and therefore requires polling. It doesn't cover auth or scale/rate behavior, but the async lifecycle disclosure is substantive.

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 tight sentences with zero filler: the action and its scope come first, and the async return plus polling instruction follow. Every clause earns its place.

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 13-parameter tool with no output schema and no required fields, the description compensates by disclosing the async return value (jobId) and the polling path. It leaves the runId/conversationId/runtimeContextId interlock to the schema, which is acceptable since those are fully documented there.

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% with 13 well-documented parameters, so the schema already carries parameter meaning. The description only loosely gestures at the persona/scenario inputs ('auto-generated or specified personas and scenarios') without adding syntax or constraint detail beyond the schema, so baseline 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 (start) and resource (simulated conversations) plus the goal (test agent performance against personas and scenarios), which is concrete and distinguishable in substance. It does not explicitly differentiate itself from adjacent simulation/testing siblings like simulate_ab_test, start_model_test, or start_production_test, so it falls short of a 5.

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 tells the agent the follow-up workflow ('use get_simulation_status to poll for results'), which is genuinely useful operational guidance. However, it gives no when-to-use vs. when-not guidance relative to the other simulation/test tools, so the alternative-selection dimension is left to inference.

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