list_active_connections

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

The description discloses the return format and field names, and clarifies that only non-system connections are listed. Since no annotations are provided, the description carries the burden well by detailing the filter and output structure.

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 consists of two short sentences and a return format example, with no padding or redundancy. Every sentence adds value.

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 has only 2 parameters, no output schema, and is a simple listing, the description sufficiently covers purpose, usage, parameters, and return value.

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 description adds significant meaning: it explains 'database' is a key from 'list_databases' and provides a regex example for 'userFilter' with case-insensitivity and default behavior. This goes 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 clearly states 'List active non-system connections to the database', specifying the verb (list), resource (connections), and scope (active, non-system). This distinguishes it from sibling tools like 'list_databases' or 'list_objects'.

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?

The description explicitly says 'Useful before running DDL or maintenance to check who is connected', providing clear context. While it doesn't list alternatives or when not to use, the usage scenario is well-defined.

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