set_run_speed

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, yet it only implies mutation via '设置' and the multiplier concept ('倍数'). It says nothing about permissions, whether the change applies immediately or to the next run, acceptable bounds, or side effects on an in-progress simulation.

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?

A single short sentence with no filler, and the core action is front-loaded. It is under-specified rather than verbose, which is penalized in other dimensions, not this one.

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?

Although the tool is simple (one required numeric parameter, no output schema), it is an unannotated mutation with no stated valid range, units, or effect on a running simulation. That leaves the agent without enough context to call it safely or predict the result.

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% and the parameter is already documented as '速度倍数，如 1 或 10', so the description adds no meaning beyond the schema. Baseline 3 applies when the schema does all the work.

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 gives a specific verb and resource ('设置运行速度倍数' – set the run speed multiplier), so the basic action is unambiguous, unlike a bare tautology. It does not, however, distinguish this from siblings such as control or get_run_state, nor clarify which 'run' (simulation run vs. webserver) is affected.

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?

There is no guidance on when to use this tool, no prerequisite such as whether a run must be active first, no valid range of speeds, and no pointer to any alternative. The agent must infer everything from the name.

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