nebula_switch_environment

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

With only readOnlyHint=false and destructiveHint=false from annotations, the description carries real weight: it discloses that failure preserves the existing session, that success resets the selected graph and pending query, and that pending queries are not executed in the new environment. These are non-obvious state effects an agent needs before calling.

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?

Four short sentences, zero filler, with the core action front-loaded and the caveats following. Every sentence adds a distinct behavioral fact.

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?

An output schema exists, so return values need not be described. The description covers failure/success semantics and scope limits, which is most of what an agent needs; it is only thin on what a valid environment name looks like and whether invalid names fail loudly.

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 0% for the single 'name' parameter, so the description must compensate. "Preconfigured environment" implies that name is an environment identifier, which is meaningful but minimal; no format, valid values, or case/matching rules are provided.

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?

Names a specific verb and resource: switch to a preconfigured environment. It also bounds the action by stating what it does not do (does not execute pending queries or switch host MCP servers). It does not explicitly contrast itself with siblings like nebula_test_connection or nebula_list_environments, so it stops short of a 5.

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?

"After testing its connection" implies this tool handles the connection test itself, which is useful implicit routing against nebula_test_connection, and the failure/success conditions give context. However, no alternative tool is named and no explicit when-not guidance is given, so usage is only implied.

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