create_simulation

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses little beyond 'creates'. It does not say whether the new simulation's ID is returned, whether re-creating the same scenario/personality pair is allowed or errors as a duplicate, what permissions are needed, or whether the simulation is immediately runnable.

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, front-loaded with the core action and immediately followed by the next-step pointer. No filler or redundancy for a simple creation tool.

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 four-parameter mutation with no annotations and no output schema, the description is only partially sufficient: it names the action and the intended follow-up, but omits return value/ID, duplicate handling, and prerequisite lookups. Adequate but with clear gaps an agent would want filled.

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 all four parameters including name, path, and the two required UUIDs; baseline 3 applies. The pairing sentence adds a small conceptual gloss on why scenarioId and personalityId are both required, but no format or constraint detail beyond the schema.

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 states a specific verb and resource ('Creates a simulation') and clarifies the domain meaning by defining a simulation as a scenario paired with a personality. It is clear on its own, though it does not explicitly differentiate itself from nearby siblings such as create_simulation_suite or create_simulation_personality.

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?

'Run it with run_simulations' gives a useful lifecycle pointer to the follow-up tool, which is real guidance. However, there is no statement of when to use this versus create_simulation_suite, and no mention that scenarioId/personalityId must first come from list_simulation_scenarios/list_simulation_personalities.

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