ServiceNow MCP Server

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

With no annotations provided, the description carries full responsibility for behavioral disclosure but offers none. It doesn't indicate whether this is a read-only or destructive operation, what permissions are required, whether it triggers workflows, what happens on success/failure, or any rate limits. The description fails to provide any behavioral context beyond the basic creation action.

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 maximally concise at a single sentence with no wasted words. It's front-loaded with the core action and resource. While severely under-specified, what's present is structured efficiently without redundancy or unnecessary elaboration.

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 complexity of a ServiceNow changeset creation tool with no annotations, no output schema, and poor schema description coverage, this description is completely inadequate. It doesn't explain what a changeset is, how it relates to other change management entities, what happens after creation, or what the tool returns. The description fails to provide the minimal context needed for effective tool use.

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 description provides zero information about parameters, while the input schema has 0% description coverage (the schema descriptions are generic like 'Name of the changeset'). With 1 required parameter (a nested object containing 4 fields), the description doesn't explain what 'params' contains, what 'application' refers to, or the relationship between name, description, application, and developer fields. It fails to compensate for the schema's lack of semantic detail.

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 'Create a new changeset in ServiceNow' is a tautology that essentially restates the tool name 'create_changeset' with minimal additional context. It specifies the verb 'create' and resource 'changeset' but provides no detail about what a changeset is, its purpose, or how it differs from similar resources like change requests or workflows mentioned in the sibling tools list.

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 provides no guidance on when to use this tool versus alternatives. With sibling tools like 'create_change_request', 'commit_changeset', 'publish_changeset', and 'update_changeset', there's no indication of the workflow context, prerequisites, or sequencing relationships. The agent receives no help in distinguishing this tool's role in the broader ServiceNow change management process.

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