fm_get_current_connection

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

The description discloses that the password is masked in the output, a key behavioral trait. No annotations are present, so the description carries the full burden. It does not mention side effects or permissions, but for a read-only get operation, the disclosure of password masking is sufficient.

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, focused sentence with no wasted words. It front-loads the action and immediately adds a crucial detail (password masked). Every word contributes meaning.

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 (no parameters, no output schema), the description covers the essential purpose and a notable behavioral detail. However, it does not specify what fields are included in 'details', which could be considered a minor gap. Sibling tools exist but are not referenced.

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 has zero parameters, and schema coverage is 100% (vacuously). According to guidelines, no parameters means baseline score of 4. The description adds no parameter info because none is needed.

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 that the tool retrieves the currently active database connection details, with a specific verb 'Get' and resource 'connection details'. It distinguishes itself from sibling tools like fm_list_connections (which lists all connections) by specifying 'currently active'.

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 implies usage when needing details of the active connection, but it does not explicitly guide when to use this tool versus alternatives (e.g., fm_list_connections for all connections, fm_set_connection to change the active one). No when-not-to-use or alternative references are provided.

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