run_simulation

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

With no annotations, the description carries the burden. It discloses the simulated mode and the random/sequential nature of the simulation, which is useful behavioral context. However, it does not explain potential side effects, output format, or resource impact, leaving gaps in transparency.

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 a single concise sentence that efficiently captures the core purpose and mode. It is front-loaded with the mode indicator, but it is so brief that it sacrifices substantive detail, still earning its place without waste.

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 the tool has 5 parameters, no annotations, no output schema, and numerous siblings, the description is too sparse. It does not explain return values, how to interpret results, or when to use this tool over other similar simulation tools, leaving significant contextual gaps.

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 0%, so the description should compensate. It only hints at 'random / sequential' which maps to the userPatterns enum, but provides no explanation for duration, intensity, or monitorMetrics. The description adds minimal parameter meaning beyond the raw 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 the tool performs user-behavior simulation with random or sequential patterns to find issues. It clearly identifies the action and resource, and the purpose differentiates it somewhat from sibling tools like run_stress_test or run_scenario_test, though it does not explicitly name alternatives.

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?

No explicit guidance is given on when to use this tool versus siblings such as run_scenario_test or run_stress_test. The description implies usage for general user-behavior simulation, but there is no mention of preferred contexts, exclusions, or alternative tools.

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