scf_delete_compensating_control

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'destructive write' is redundant. It does add one useful piece of context—the 'editor role' requirement—but it does not disclose irreversibility, cascading effects, or what happens if the record is not found. With annotations covering the core safety profile, this is adequate but not rich.

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, but the parenthetical 'destructive write' repeats what annotations already state. The 'editor role' part is valuable. Overall compact, with a minor redundancy preventing a 5.

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 operation, the definition is largely complete: the resource is clear, the destructive nature is covered by annotations, the role is stated, and all parameters are fully described in the schema. It could add a note on permanence or cascading effects, but these are minor given the annotations.

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 description coverage is 100%, with each UUID parameter already documented including how to obtain it (e.g., 'obtain from scf_list_compensating_controls'). The description itself adds no parameter semantics, so the baseline of 3 applies.

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 uses a specific verb ('Delete') and names an exact resource ('vendor compensating control record'), which distinguishes it from sibling delete tools like scf_delete_vendor_certification or scf_delete_vendor_action_item. The title also reinforces the resource. No ambiguity about what operation this performs.

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 gives no guidance on when to choose this tool over alternatives such as scf_update_compensating_control or scf_list_compensating_controls. The intended use is only implied by the verb 'Delete'; there are no conditions, exclusions, or mentions of related siblings.

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