ServiceNow MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool publishes a changeset but doesn't explain what this entails—such as whether it's a destructive operation, requires specific permissions, has side effects (e.g., affecting live systems), or includes rate limits. This leaves critical behavioral traits unspecified for a mutation tool.

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, direct sentence with no wasted words. It's appropriately sized for a simple tool name and efficiently conveys the core action and resource. The structure is front-loaded, making it easy to parse quickly.

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 mutation tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It doesn't explain what 'publish' means behaviorally, what the parameters do, or what the tool returns. For a tool that likely modifies system state, this lack of context is a significant gap.

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 adds no parameter information beyond what the input schema provides. Schema description coverage is 0%, meaning parameters are undocumented in both the schema and description. However, there is only 1 required parameter ('changeset_id'), which reduces complexity. The baseline score of 3 reflects minimal viability given the low parameter count, but no value is added over the schema.

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 the action ('publish') and resource ('a changeset in ServiceNow'), which provides a basic understanding of what the tool does. However, it doesn't specify what 'publish' means operationally (e.g., deploying changes, making them live) or differentiate it from similar tools like 'commit_changeset' or 'update_changeset' in the sibling list. This makes the purpose somewhat vague but not misleading.

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 offers no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., whether a changeset must be committed first), exclusions, or comparisons to sibling tools like 'commit_changeset' or 'update_changeset'. Without any usage context, the agent lacks direction on appropriate invocation scenarios.

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