Get change request conflict

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered by structured data. The description does add genuine behavioral context: it enumerates error conditions (MissingParameterError when change_request_sys_id is absent, ParameterError on invalid params/JSON) and states the return is a parsed Pydantic model. It stops short of describing pagination or what conflict fields are returned.

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 the first line, which is good, but the remainder is raw docstring boilerplate (:param/:type/:return/:rtype/:raises) aimed at a Python reader rather than an agent, with a redundant :rtype: Response line. It is short, but not every line earns its place.

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 optional-looking parameters, no output schema, and 0% schema description coverage, the definition is far too thin for the tool's complexity. The return description ('parsed Pydantic model with information about the conflicts') is a small help since no output schema exists, but 21 undocumented parameters and no filtering guidance leave an agent unable to call this correctly beyond the single sys_id argument.

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% across 22 parameters, so the description carries the full documentation burden, yet it documents only change_request_sys_id and ignores the other 21 (state, change_type, model_sys_id, sysparm_query, response_length, refresh_impacted_services, etc.). It adds no format, default, or filtering semantics beyond the one field, leaving most parameters opaque.

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 opening sentence gives a specific verb+resource: 'Retrieve conflict information associated with a change request.' An agent immediately knows the operation and the target entity. However, it does not distinguish this from close siblings such as servicenow_check_change_request_conflict or servicenow_delete_change_request_conflict_scan, leaving the retrieval-vs-scan distinction to inference.

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 statement of when to use this tool versus the sibling conflict tools (check_change_request_conflict, delete_change_request_conflict_scan), no prerequisites, and no guidance on what a retrieved conflict means or how to act on it. Usage must be inferred entirely from the name.

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