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

Annotations already declare destructiveHint=true and idempotentHint=true, so the irreversibility claim ('the change cannot be undone') mostly restates structured data. It does add a caller-side safety step (verify the identifier first), but says nothing about cascade effects on runs/personas or what a successful response contains.

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 short sentences, front-loaded with the action and followed by the one safety-relevant warning. No filler, nothing that could be cut without losing information.

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 single-parameter destructive delete with annotations covering the safety profile, this is minimally adequate. It omits the practically important question of whether deleting a simulation also removes its runs, personas or scenarios, which an agent must know before invoking an irreversible operation.

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 100% and the id property already documents its format, pattern and provenance, so the schema carries the semantics. The description only reinforces 'review the identifier' without adding format or origin detail beyond the schema baseline.

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 (delete) and resource (simulation), which separates it from the many delete_* siblings such as delete_simulation_run and delete_simulation_persona. The demonstrative 'this simulation' is slightly off-key for a tool taking an arbitrary id, but the intent is unambiguous.

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 guidance on when to delete versus when to update or archive, no prerequisites or permission notes, and no mention of the sibling delete_simulation_scenario/delete_simulation_persona that an agent might confuse it with. The only instruction is a generic caution to verify the id.

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