database_switch_environment

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states the high-level action but does not explain side effects, such as whether switching closes existing connections, changes the default environment for subsequent commands, or requires an active connection. This is insufficient 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, concise sentence that is immediately understandable. Every word earns its place, and there is no redundant or verbose phrasing.

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 the tool's simplicity (one parameter, no output schema), the description is minimally adequate. However, the presence of similar sibling tools like 'database_connect_environment' and the lack of usage guidance or behavioral nuance make it incomplete for an agent to confidently select and invoke the tool without ambiguity.

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% and the parameter 'environmentName' is described as 'Name of the environment to switch to'. The description adds only the word 'detected', which provides minor context that the environment must already be known, but it does not add substantive meaning beyond 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?

The description 'Switch to a different detected database environment' clearly states the action (switch) and the resource (database environment), and adds 'detected' to indicate it operates on already known environments. However, it does not differentiate from the sibling tool 'database_connect_environment', which may have a similar purpose.

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?

There is no guidance about when to use this tool versus alternatives like 'database_connect_environment' or 'database_list_environments'. The description implies it is used after detection but does not state prerequisites, behavior relative to current sessions, or exclusions.

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