Cancel Simulation

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

Adds details beyond annotations: mentions SIGTERM, immediate stop, preservation of partial action log, and that post-cancellation calls to get_report or simulation_data are still valid. Annotations already indicate destructiveness, but description elaborates.

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?

Two sentences: first states action and mechanism, second lists use cases. No wasted words.

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?

Complete for a simple cancellation tool. Explains behavior, side effects, and post-cancellation capabilities. Output schema not needed.

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?

Only one parameter with full schema coverage. Description does not add meaning beyond the schema's description, which is adequate given simplicity.

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?

Description clearly states verb 'Stop a running simulation' and resource 'simulation'. It distinguishes from siblings like create_simulation and get_report by focusing on cancellation.

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 specifies when to use: 'when a simulation is taking too long, was started by mistake, or is producing bad output you want to abort.' Provides clear context.

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