list_databases

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

Annotations already establish read-only behavior. The description adds meaningful context by clarifying that results are limited to databases the profile's login can open and by indicating the visible attributes such as state and size, which helps explain the access-scoped result set. It does not cover ordering, pagination, or performance traits.

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?

A single carefully constructed sentence front-loads the resource and scope, then lists the returned fields. There is no wasted text.

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?

With an output schema and full parameter schema coverage, the description does not need to explain return formatting. It covers the access scope and content of the listing, though it could be more complete by mentioning when to choose this over sibling list tools.

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 single profile parameter already documents that it comes from list_profiles. The description adds no further parameter guidance, so the schema does the heavy lifting and the baseline of 3 is appropriate.

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?

States a specific list action on databases and adds useful scoping detail: only databases this profile's login can open, plus the fields returned. It does not explicitly contrast with siblings such as list_tables, but the resource is clear enough to distinguish them.

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 use when an agent needs available databases for a profile, especially since the required profile parameter references list_profiles. However, it never states when to prefer this over list_tables or other list tools, nor any exclusions or prerequisites beyond the schema.

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