destroy_simulation

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

No annotations provided, so the description carries the full burden. It discloses that the tool frees memory and that simulations persist until destroyed, which is important for understanding side effects and server resource management.

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?

Well-structured with sections (Description, Args, Returns, Tips, Example). Each sentence adds value, though slightly longer than strictly necessary. Tips for LLMs are helpful.

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, return value, usage guidelines, and behavioral impact. No output schema needed; the description adequately explains what the tool does and what to expect.

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 coverage is 0% (no descriptions in schema), but the description adds 'sim_id: Simulation ID to destroy' and includes an example, providing clear meaning beyond the raw type.

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 clearly states 'Destroy a simulation and free resources' with a specific verb and resource. It distinguishes itself from sibling tools like create_simulation and step_simulation by focusing on cleanup.

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 says 'Cleanup when done with a simulation' and 'Always destroy simulations when conversation ends or changes topic.' Provides clear when-to-use guidance and implies not to use while simulation is still needed.

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