simulator_disconnect

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

Description lacks detail beyond disconnection behavior. No disclosure of prerequisites (e.g., must be connected), side effects (e.g., ongoing actions stopped), or safety. Annotations do not compensate (destructiveHint=false is generic). Could mention that it is a graceful shutdown.

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?

Single sentence, front-loaded, no unnecessary words. Efficient and clear.

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 parameterless action, description is mostly adequate. However, could include brief note on typical preconditions (e.g., simulator must be connected) to enhance completeness.

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?

No parameters exist (schema coverage 100%). Description correctly adds no param info. Baseline for 0 params is 4.

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 action: stop autonomous control and disconnect. Specifies it does not force quit, distinguishing from potential force-quit tools. Differentiates from sibling tools like simulator_connect and emergency_stop by describing a graceful disconnect.

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?

Implies usage when wanting to disconnect without quitting, but no explicit when-to-use, when-not-to-use, or comparison to alternatives like emergency_stop or autonomy_stop. Agent must infer appropriate context.

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