select_instance

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

No annotations are provided, so the description carries full burden. It discloses the key stateful behavior (subsequent calls are routed/re-routed to the selected instance) and the reset escape hatch (port=0), which are non-obvious and valuable. It stops short of describing failure modes or whether the current selection persists across sessions.

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?

Front-loads the core action and effect in the first sentence, with reset instructions in a short second paragraph. Slightly repetitive with "call select_instance" recited twice, but there is little waste overall.

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 3-parameter, annotation-free, output-schema-free routing tool, the description supplies the routing effect, discovery pointer, and reset behavior an agent needs. It omits error handling and does not address the host parameter, but it is adequate to invoke correctly.

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 coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: the reset semantics of port=0 and the instruction to derive the port from the current instance. The host parameter is left to the schema.

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?

States a specific verb and resource ("Switch to a different IDA Pro instance") and immediately clarifies the effect (all subsequent calls routed to the selected instance). It distinguishes itself from the sibling list_instances, which only enumerates instances, so an agent can tell the two apart without opening schemas.

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?

Explicitly routes the agent to list_instances to discover available instances and gives the switch-back/reset conditions (pass this instance's port, or port=0). It covers the main when-to-use flows but does not state error conditions or what happens when the target is unavailable.

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