servicenow-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions a prerequisite (SCRIPTING_ENABLED=true) which is useful, but doesn't describe what 'commit' actually does - whether it's a write operation, if it's reversible, what permissions are required, or what happens to the update set after committing. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise at just 8 words, front-loading the core purpose immediately. Every word serves a purpose - the first half states the action, the second half provides a critical prerequisite. There's zero waste or redundancy.

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 mutation tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what 'commit' means operationally, what state changes occur, what permissions are needed beyond the scripting flag, or what the tool returns. The prerequisite is helpful but doesn't compensate for the missing behavioral context needed for safe invocation.

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 100% with the single parameter 'sys_id' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's in the schema, which is acceptable given the high schema coverage. The baseline score of 3 reflects adequate but not enhanced parameter documentation.

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 tool's purpose as 'Commit an update set', which is a clear verb+resource combination. However, it doesn't differentiate from sibling tools like 'complete_update_set' or 'publish_changeset', leaving ambiguity about how this specific commit operation differs from other update set operations.

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 minimal guidance with the prerequisite 'requires SCRIPTING_ENABLED=true', but offers no context about when to use this tool versus alternatives like 'complete_update_set' or 'publish_changeset'. There's no mention of workflow stages, dependencies, or typical scenarios for committing changesets.

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