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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'Cancel' is consistent. The description adds the useful detail that the tool targets running or pending simulations, but it does not disclose other behavioral implications such as irreversibility or effect on results. Given annotation coverage, this is adequate but not rich.

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?

The description is a single, front-loaded sentence with no extraneous words. It immediately states the action and target, keeping the most important information first and avoiding any waste.

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 simple, one-parameter destructive tool with annotations covering the destructive nature and no output schema, the description is sufficient. It names the target state (running or pending) and requires nothing beyond the simulation ID to invoke correctly.

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 schema description coverage is 100% and the sole parameter simulationId is described as 'Simulation ID.' The description adds no additional semantic explanation beyond the schema, so it meets the baseline for full schema coverage without further value.

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 the verb 'Cancel' and the resource 'simulation' with the specific state qualifier 'running or pending.' This distinguishes it from sibling tools like lexq_simulation_start, lexq_simulation_status, and lexq_replay_cancel without ambiguity.

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 description provides some context by specifying 'running or pending' simulations, implying it applies only to active simulations. However, it does not explicitly mention alternative tools or when not to use this tool, leaving some inference required for routing to siblings like replay_cancel.

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