connect_servicenow

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

With no annotations provided, the description must disclose behavioral traits. It mentions that credentials are 'held in memory for this session only — never stored or logged,' which is a key security detail. However, it does not describe potential side effects like overwriting an existing connection, error handling, or whether the tool tests connectivity before returning.

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 well-structured with a one-line purpose, separate sections for WHEN TO CALL and HOW TO ASK THE USER, and a follow-up instruction. It is front-loaded with the main purpose, concise, and every sentence adds value.

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 no output schema, the description instructs the agent to tell the user whether the connection succeeded and which instance was connected to, providing a complete flow. However, it omits details about error conditions or the exact return format, which would enhance completeness.

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 each parameter already described in the input schema. The tool description repeats these parameters in a user-facing format but adds no new semantic meaning beyond the schema, only the security note which pertains to behavior rather than parameter semantics.

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 states 'Connect to a ServiceNow instance in one step,' specifying the verb (connect) and resource (ServiceNow instance). This distinguishes it from sibling tools like connect_jira and connect_salesforce, making the tool's purpose unambiguous.

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 includes a 'WHEN TO CALL' section that explicitly states to call at the start of any session needing ServiceNow access or when get_config shows servicenow.configured = false. This provides clear context for when to use the tool, though it does not list alternatives or exclusions explicitly.

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