Check change request conflict

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

Annotations are supplied (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), so the safety profile is partly covered. The description adds error behavior (:raises MissingParameterError / ParameterError) and the return type, which is useful, but it never explains the side effects implied by readOnlyHint=false and idempotentHint=false (e.g., whether a conflict scan record is created or state is mutated).

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 sentence is front-loaded and the docstring is reasonably compact, but it carries boilerplate noise (:rtype Response, ParameterError listed twice) and does not spend its limited space on the information an agent actually needs.

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 22-parameter tool with no output schema and zero schema descriptions, the definition is far too thin; it leaves the agent without the parameter meanings, filtering semantics, or response shape needed to invoke it correctly.

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 0% and there are 22 parameters, of which only change_request_sys_id is documented ('Sys ID of the change request'). The remaining parameters (data, state, change_type, cmdb_ci_sys_ids, sysparm_query, etc.) are entirely unexplained in both schema and description.

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 states a specific verb+resource: 'Check for conflicts in a change request.' That is enough for an agent to know the operation, but it does not distinguish this tool from close siblings such as servicenow_get_change_request_conflict or servicenow_delete_change_request_conflict_scan, so sibling differentiation is missing.

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?

There is no guidance on when to use this tool versus alternatives. Given the crowded sibling set (get_change_request_conflict, delete_change_request_conflict_scan, create_change_request), the absence of any routing or prerequisite information is a real gap.

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