delete_scenario

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

The description does not disclose any side effects, such as whether deletion is permanent, cascades to related entities, or requires confirmation. No annotations are provided to fill this gap, so the tool's behavior remains opaque.

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 short sentence with no unnecessary words, which is concise. However, it is too terse to be considered well-structured for an agent, as it omits critical usage details that would typically be part of a complete description.

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?

With only two parameters and a simple operation, the description still fails to provide necessary context such as the effect of deletion, any dependencies, or error conditions. This makes the tool inadequate for an agent to use confidently without external knowledge.

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 provides a description for 'project' but not for 'scenarioId'. The description adds no additional meaning to either parameter, leaving 'scenarioId' undefined and not clarifying how it relates to the action.

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 states the primary action ('Delete') and the resource ('a scenario'), which clearly identifies the tool's purpose. However, it lacks additional context about the scenario's identity or scope, making it clear but not highly informative.

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 is provided about when to use this tool versus alternatives like 'create_scenario' or 'list_scenarios'. The description does not mention any conditions, prerequisites, or scenarios where deletion is appropriate.

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