connect_servicenow

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

The description provides no behavioral details beyond the verb 'Connect'. No annotations exist. It fails to disclose side effects (e.g., storing session tokens), required permissions, or success/failure conditions, leaving significant ambiguity for a state-changing 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 sentence with no redundant words. It efficiently communicates the core purpose without 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?

For a tool with no parameters and no output schema, the description is minimal. It omits essential context like prerequisites (e.g., network access, credential storage), behavior after connection (e.g., persistent session), and how to verify success. More detail would aid agent decision-making, especially given the tool's role as a gateway to other ServiceNow tools.

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 input schema has zero parameters, but the description mentions 'using your username and password', implying stored credentials. This adds meaningful context beyond the empty schema, though it is not formalized as parameters. Schema coverage is trivially 100%, baseline 3, but added context justifies a 4.

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 clearly identifies the action ('Connect') and the resource ('ServiceNow instance'), distinguishing it from sibling tools like 'disconnect_servicenow' and ServiceNow operation tools. However, it does not specify what 'connect' entails (e.g., establishing a session or authentication context).

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?

No guidance is provided on when to use this tool or its prerequisites. Given it is a connection tool for a suite of ServiceNow operations, it should state that it must be run before other ServiceNow tools. Absent any such direction.

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