switch_instance

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

Adds 'for this session' beyond annotations, indicating state change scope. Annotations already note idempotency and open-world, but description could disclose side effects like losing unsaved work.

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?

Single concise sentence with no wasted words, front-loading the core action.

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?

Covers the essential purpose and scope for a simple tool with one parameter and good annotations; could be slightly more explicit about session persistence.

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 provides full description of the 'name' parameter (e.g., 'prod', 'dev'), and main description does not add additional meaning beyond that.

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?

Description uses specific verb 'switch' and resource 'active ServiceNow instance', clearly distinguishing from siblings like 'get_current_instance' (read-only) and 'switch_update_set' (different resource).

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?

Implies usage for changing the active instance for the session, but lacks explicit guidance on when to use vs alternatives or potential prerequisites (e.g., having configured instances).

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