set_connection

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

No annotations are provided, so the description carries the full disclosure burden, which it does not meet. It does not say whether the connection is validated on set, what happens on an invalid string, whether the change persists across calls or sessions, or that it handles credentials in plaintext. Only the format of the argument is disclosed.

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?

Two short, front-loaded sentences with no filler; the core behavior comes first and the argument format follows. The Google-style 'Args:' block is slightly redundant for a one-parameter tool but still earns its place as the format example.

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, and a single-parameter tool is inherently simple. What is still missing is the stateful consequence of the call: whether the switch applies to subsequent execute_readonly_query calls, whether it is per-session, and what failure looks like.

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% – the schema only titles the field 'Connection String' with no description. The description compensates by giving a concrete format example ('user/password@host:1521/service_name'), which tells the agent exactly what shape of value to supply, including credentials, host, port and service name.

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 gives a specific verb and resource: it 'sets or switches the active Oracle database connection string.' The word 'active' and 'dynamically' distinguish it from the read-only introspection siblings, none of which manage connection state. However, it never explicitly contrasts itself with siblings such as get_connection_info, so it falls just 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?

There is no guidance on when to call this tool, whether it must be called before execute_readonly_query, or how it relates to get_connection_info. The only usage hint is the implicit sense of 'active' (session state changes), with no exclusions, prerequisites, or alternatives named.

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