close_simulation

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

With no annotations, the description carries the full burden of behavioral disclosure and does not meet it. 'Close' implies a state-changing operation, but it never says whether waveform/signal data is lost, whether unsaved results are discarded, whether an error is raised if no simulation is open, or whether the enclosing session/project stays intact. Only the bare mutation is named.

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?

One short, front-loaded sentence with zero filler. Nothing is repeated and the resource being acted on is stated immediately.

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?

The tool is structurally simple (no params, no output schema, no annotations), so a short description is defensible. However, even for a no-arg lifecycle tool the agent needs to know what 'close' does to simulation state and whether it is safely re-callable, and the description leaves both open.

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 takes zero parameters (empty properties, no required fields), so there is nothing for the description to disambiguate. Baseline of 4 applies for a no-argument tool.

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?

States a specific verb ('close') and a specific resource ('the current simulation'), so the agent can tell it apart from launch_simulation, run_simulation and restart_simulation. It stops short of explicitly contrasting with the closest sibling, restart_simulation, which would have earned a 5.

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?

The word 'current' implicitly signals the precondition that an active simulation must exist, which is a usable usage cue. But there is no explicit when-to-use guidance, no statement of what to do instead if you want to keep the session alive (restart_simulation), and no exclusions.

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