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

The description adds valuable behavioral context beyond the annotations: credentials are entered directly in Local MCP's settings window and never passed through the AI, and the tool returns a link rather than accepting credentials directly. This is important for safe usage and is not expressed by the schema or annotations.

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 short and front-loaded, with the key behavioral note about security placed in the second sentence. The opening phrase 'Connect ServiceNow' is somewhat redundant with the title, but the rest of the description is efficient and every sentence contributes actionable guidance.

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 zero-parameter setup tool with an output schema and annotations, the description is complete enough: it tells the agent what action to take, what link to expect, and how the user should complete the connection. It does not explain post-connection status, but the output schema can cover return details.

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 tool has zero parameters, so the baseline is 4. The description reinforces this by explaining that the user enters credentials in a separate settings window, not through the tool call. This helps prevent the agent from prompting for credentials or fabricating parameters.

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 a clear verb and resource: connect to ServiceNow, and explains the immediate outcome (get a link). It does not explicitly contrast with sibling connection tools like connect_chatgpt or disconnect_servicenow, so it loses a point on differentiation, but it is unambiguous about what this tool initiates.

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 gives explicit usage steps: call this to get the link, then open it and enter instance, username, and password. It clearly communicates when to use the tool and what the user must do afterward, though it does not mention alternatives or exclusion criteria such as using disconnect_servicenow to undo the connection.

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