Delete change request conflict scan

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The description adds the error behavior (MissingParameterError, ParameterError on bad params/JSON) and the return shape, which is useful beyond the annotations, but says nothing about what is irreversibly removed or the auth scope.

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 purpose is front-loaded in one clear sentence, and the docstring blocks are orderly, though the duplicated ParameterError entry and verbose :type/:rtype lines add minor noise.

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 22 parameters, no output schema, and 0% schema description coverage, the definition is substantially incomplete for correct invocation — most of the accepted parameters are unknown in purpose and format, and the required-argument semantics are fuzzy.

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 coverage is 0% across 22 parameters, so the description carries the full burden. It documents only change_request_sys_id and task_sys_id, leaving roughly 20 parameters (state, change_type, model_sys_id, sysparm_limit, cmdb_ci_sys_ids, etc.) completely undescribed; the raises clause is also ambiguously worded about whether one or both IDs are required.

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?

States a specific verb+resource: deleting conflict-scan information tied to a change request. It clearly differs from siblings like servicenow_get_change_request_conflict and servicenow_check_change_request_conflict, though it never explicitly names or contrasts them.

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 on when to delete vs. re-scan or use servicenow_check_change_request_conflict. The only conditional information is the raises clause about a missing identifier, which hints at a requirement but does not frame usage or alternatives.

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