mssql_list_databases

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds the 'online' scoping detail, but omits important behavioral context such as whether it returns system databases, whether authentication is needed, what happens when parameters are omitted, and what the output format looks like.

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, front-loaded sentence with no filler or repetition. It is concise and immediately states the core action, though it sacrifices useful parameter and usage detail for brevity.

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?

For a tool with no annotations, no output schema, and two undocumented parameters, the description is too sparse. An agent cannot fully determine how to invoke the tool correctly, what the parameters mean, or what the result will contain, leaving significant room for misconfiguration.

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 schema has 0% description coverage and the description does not mention the 'server' or 'database' parameters at all. While 'server' is mildly self-explanatory, the 'database' parameter is confusing for a tool that claims to list all online databases, and an agent cannot determine whether it filters the listing or merely specifies connection context.

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 names a specific verb ('List') and resource ('all online databases') on the MS SQL Server, making the tool's purpose immediately clear. It is naturally distinct from siblings like mssql_list_tables and mssql_execute_query because it targets database enumeration at the server level.

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 gives no guidance about when to choose this tool over alternatives, such as when to use mssql_test_connection versus listing databases or when to use mssql_list_tables once a database is selected. The usage context is only implied by the tool's name and basic purpose, not stated.

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