df_get_connection

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds context that include_db_schema=true returns a 'full cached table/column schema', but it does not explain the cache mechanics or how use_cache interacts with this behavior.

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 concise sentences front-load the core purpose and then provide the key optional behavior. There is no redundant or irrelevant text.

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?

This is a moderately complex tool with six parameters Alert: The description lacks clarity on language and use_cache, does not fully explain connection_id, and only partially describes the return shape. The absence of an output schema raises the burden on the description, which is not met.

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?

With only 33% schema description coverage, the description needs to compensate. It adds meaning for include_db_schema, but language and use_cache remain unexplained, and connection_id is only implicitly defined. The return-field list is helpful but does not clarify the input parameters enough.

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 clearly states the tool retrieves a single connection and enumerates the key fields returned (host, port, database, schema, username). It does not explicitly differentiate from siblings like df_list_connections or df_get_connection_schema, but the singular 'one connection' narrows the scope.

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 explicit guidance on when to use this tool versus alternatives. The only conditional guidance is the include_db_schema flag explanation, which addresses a parameter rather than tool selection; no exclusions or sibling comparisons are provided.

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