test_connection

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

No annotations are supplied, so the description carries the behavioral burden. It discloses the operation's output surface (version, database name, user, schema, instance) and implicitly frames it as a non-mutating diagnostic, but says nothing about failure behavior (e.g., whether an unreachable DB raises an error or returns a status field) or timeout characteristics.

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 sentences, zero filler. The purpose and its output payload lead, and the call-condition guidance follows immediately as a labeled block, making the front-loaded structure easy to scan.

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?

With no output schema and no parameters, the description must supply the return surface itself, and it does so by naming the five reported values. Combined with the explicit usage boundary, an agent has everything needed to call this correctly and to avoid calling it unnecessarily.

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?

The tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate beyond confirming no input is required, which the empty schema already shows.

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 opens with a specific verb+resource ('Verify connectivity to Oracle') and enumerates exactly what is reported: database version, name, current user, current schema and instance name. This cleanly separates it from the introspection-heavy siblings (list_*, get_*, describe_*) that query objects rather than the connection itself.

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?

It gives an explicit positive condition ('only when the user explicitly asks to verify the connection or diagnose reachability') and an explicit negative ('do NOT call as a preamble before answering a query about tables, data, or schema objects'). This is precisely the routing guidance an agent needs to avoid over-calling a connectivity probe.

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