disconnect_simulator

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It omits critical details: whether disconnecting affects running simulations, idempotency (safe to call if already disconnected), error conditions, or what the output schema represents.

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?

Extremely concise single sentence with zero redundancy. Appropriate length for a parameter-less utility function where the operation is self-evident from the name and description.

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?

While the output schema reduces the need to describe return values and there are no parameters to document, the description lacks essential context for a state-changing operation: prerequisites (must be connected), side effects on the simulation state, and differentiation from 'shutdown_simulator'.

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?

The tool accepts zero parameters, triggering the baseline score of 4 per evaluation rules. No additional parameter context is needed or provided.

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 uses a specific verb ('Disconnect') and clear resource ('SimVision bridge'), distinguishing this from sibling 'connect_simulator'. However, it doesn't clarify the distinction from 'shutdown_simulator' or explicitly state this is the inverse operation of connecting.

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 provided on when to use this tool versus alternatives, or prerequisites such as requiring an active connection first. The description states what it does but not when to do it.

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