mongo_list_databases

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

With no annotations, the description carries the burden of behavioral disclosure. 'List' implies a read-only operation, but the description does not explicitly state that it makes no changes, requires an existing connection/session, or how session_name affects execution. It adds minimal context and is not misleading, but it leaves important behavioral details unstated.

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 clear sentence with no wasted words. It states the operation and the output target immediately, making it easy for an agent to parse and act on.

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 is simple and has an output schema, so return values need not be described. However, the description omits important operational context such as the role of session_name, whether an active connection is required, and how this tool relates to mongo_list_collections. It is minimally viable but leaves gaps for correct invocation in a multi-session environment.

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 description coverage is 0%, so the description must compensate for the undocumented session_name parameter, but it does not mention it at all. The parameter name 'Session Name' and its default value offer some clue, but the description adds no semantic value about how session_name is used or why it matters.

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 uses a specific verb and resource: 'List MongoDB database names.' It clearly indicates what the tool returns and distinguishes it from sibling tools like mongo_list_collections and db_list_tables by explicitly naming databases. However, it does not explicitly contrast itself with those siblings, so it stops short of a top score.

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?

No guidance is given about when to use this tool versus alternatives such as mongo_list_collections or db_list_tables. There is no mention of prerequisites like an active connection or session, nor any exclusions or preferred usage context. The usage is only implied by the name and description.

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