List Remote DB Connections

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

No annotations are provided, so the description must disclose behavioral traits. It only states that the tool lists remote database connections, without explaining whether it is read-only, what it returns, or any side effects. The description doesn't even confirm that it lists all connections or if any filtering applies.

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 concise sentence that clearly states the action and resource. It avoids redundancy and is front-loaded with the verb. There is no unnecessary information or filler.

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?

The tool has no output schema and no annotations, so the description needs to provide enough context for the agent to understand what the tool does and returns. It only restates the title and lacks details about the response format or the nature of remote database connections. The description is too sparse to be fully complete for an agent invoking this tool.

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 input schema has 100% description coverage for the single parameter (username), so the schema already explains it. The description adds no additional meaning beyond the parameter's existence, but the baseline of 3 is appropriate since the schema is self-sufficient.

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's function: listing remote database connections. It uses a specific verb (list) and resource (remote database connections), distinguishing it from sibling tools like hosting_db_list which list general databases. The word 'remote' differentiates it from other database tools in the sibling set.

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 use this tool versus alternatives. It does not mention that it returns a list of remote DB connection entries, nor does it reference related tools for creating or deleting remote connections. The usage context is only implied by the tool's name and sibling set.

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