delete_decision_flow

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. 'Permanently delete' conveys irreversibility, which is valuable context. However, it does not mention any other effects (e.g., cascading deletion of revisions, impact on published flows) or permission requirements.

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, front-loaded sentence with no filler. It efficiently communicates the core action and target without redundancy.

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?

Given the tool's simplicity (one parameter, output schema exists), the description is nearly complete. It explicitly notes permanence, and the parameter schema handles the rest. Minor gaps exist around conditions for deletion, but the current wording is adequate for a simple delete 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?

The tool description itself does not describe parameters, but the input schema provides 100% coverage with a helpful description for decision_id (UUID not name). Per the baseline, schema coverage >80% yields a score of 3; the schema adds meaning and clarifies the distinction.

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) and the target resource (SAS Intelligent Decisioning flow), using a specific verb. It distinguishes this tool from siblings like get_decision_flow, update_decision_flow, and list_decision_flows by the destructive nature.

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 for deleting decision flows but provides no explicit guidance on when to use this tool versus alternatives. There is no mention of prerequisites such as whether the flow must be unpublished or locked, nor exclusions.

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