servicenow-mcp

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 'List' which implies a read-only operation, but doesn't cover critical aspects like pagination behavior, default sorting, error conditions, or whether it requires specific permissions. This leaves significant gaps for a tool with no annotation support.

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, efficient sentence with no wasted words. It's appropriately front-loaded with the core functionality, 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?

For a list tool with 2 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what a 'mobile app configuration' entails, what fields are returned, how results are paginated (especially with the 'limit' parameter), or error handling. The lack of behavioral context makes it incomplete for effective 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?

Schema description coverage is 50% (only the 'active' parameter has a description). The tool description doesn't mention any parameters, so it adds no semantic value beyond what the schema provides. With 2 parameters and partial schema coverage, this meets the baseline of 3 where the schema does some work but gaps remain.

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 'List ServiceNow mobile app configurations' clearly states the action (list) and resource (mobile app configurations), which is adequate. However, it doesn't differentiate from potential siblings like 'get_mobile_app_config' (singular retrieval) or 'create_mobile_app_config' (creation), leaving the scope somewhat vague.

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 siblings like 'get_mobile_app_config' (singular retrieval) and 'create_mobile_app_config' (creation), there's no indication that this tool is for listing multiple configurations, nor any prerequisites or exclusions mentioned.

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