Delete a scenario

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

Annotations already include destructiveHint: true and readOnlyHint: false, so the destructive nature is known. The description adds valuable context by stating 'permanently removes' and 'Requires PROFITLEE_API_TOKEN', giving the agent important behavioral and authentication details beyond the annotations.

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 exceptionally concise, consisting of two sentences that immediately state the action and key constraints. There is no fluff or redundant details, making it easy for an agent to parse quickly.

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?

This is a simple one-parameter tool with a clear description, comprehensive annotations, and an output schema. The description covers the purpose, permanence, account requirement, and authentication. There is nothing missing for an agent to correctly invoke this tool.

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 input schema fully describes the only parameter 'id' with a rich description of its provenance (returned by list_scenarios or save_scenario). The tool description adds no additional parameter semantics beyond echoing 'by id', so the schema carries the information, meriting a baseline score of 3.

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 action ('Delete'), the resource ('one saved Profitlee scenario'), and the method ('by id'). This distinguishes it from sibling tools like list_scenarios, get_scenario, and update_scenario, which have different verbs or purposes.

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 clear context: it is for permanently removing a scenario from the authenticated Pro account, and it requires PROFITLEE_API_TOKEN. While it does not explicitly mention alternatives or exclusions, the purpose is unambiguous enough for an agent to know when to use this tool.

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