delete_scenario

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

Discloses the key behavior of not deleting files on disk, but lacks details on side effects, permissions, or reversibility. With no annotations, the description provides moderate transparency.

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?

Short and front-loaded description. The parameter section is somewhat redundant with the schema but not excessively so. No unnecessary 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?

For a simple delete tool with one parameter and an output schema, the description covers the essential behavior (removes from memory, not disk) and return value. Could mention error handling but overall sufficient.

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 parameter 'scenario_id' is described as 'UUID of the scenario to remove', adding meaning beyond the schema's type and title. However, no format constraints or examples are given.

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?

Clearly states the action (remove a scenario from memory) and distinguishes from file deletion. Specific verb 'remove' and resource 'scenario' are 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?

Implied usage: use when needing to remove a scenario from memory without deleting files. No explicit when-not-to-use or alternatives among siblings like 'delete_platform' or 'remove_component'.

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