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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is largely covered. The description reinforces this with "the change cannot be undone," which is useful emphasis but adds little beyond the destructive hint, and it says nothing about cascade effects on linked runs or dependent resources.

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 with the action front-loaded and the irreversibility warning immediately after. Every clause earns its place; nothing is padded.

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 tool with full schema coverage and annotations carrying the safety profile, this is close to sufficient. The only gap is that it doesn't clarify whether deletion cascades to dependent simulation runs or whether the resource can be recreated.

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% with a single, fully documented required parameter, so the schema does the heavy lifting. The description contributes a light but relevant directive ("review the identifier before deleting") that stresses the identifier must be correct before a destructive call.

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 and resource ("Delete this simulation scenario"), which cleanly separates it from get_simulation_scenario and update_simulation_scenario in the sibling list. It does not explicitly name those siblings, but the CRUD verb makes the distinction obvious.

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 implies usage (you delete when you want the scenario gone) and adds a caution to review the identifier first, but it offers no explicit when-to-use framing and no alternatives such as archiving or updating instead. Usage is inferable rather than stated.

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