start_simulator

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

Describes what sim.exe does, registry modification when enforce_security=False, and potential blocking if security is enabled without password-protected app. Lacks idempotency and error handling details.

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?

Three sentences efficiently convey purpose, parameter behavior, and usage restriction. No redundant or unnecessary text.

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?

Covers purpose, parameter, and usage constraint. Lacks return value specification and prerequisites (e.g., Control Expert installation). Despite that, sufficiently complete for a simple tool.

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?

With 0% schema coverage, the description fully explains the 'enforce_security' parameter: default false, its effect on registry, and why it avoids a warning dialog. Adds significant value beyond 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?

Clearly states the tool starts the Control Expert PLC simulator (sim.exe) for plc_connect to reach it. Distinguishes itself by focusing on starting, unlike sibling stop_simulator.

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?

Explicitly restricts use to 'only on a local test machine.' Explains default behavior and when enforce_security matters. No explicit comparison to non-sibling tools, but context is clear.

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