list_databases

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only mentions that databases are 'accessible,' which gives minimal context but does not explain pagination, search behavior, or the full structure of the response, leaving important behaviors undocumented.

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 extremely concise, one sentence with no wasted words. However, it could have used this brevity as an opportunity to add a bit more practical detail without harming clarity.

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, so the description should explain return values and behaviors. It only states that IDs are included, without mentioning other fields or the paginated response structure, making it incomplete for an agent relying solely on this description.

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 description provides no additional meaning for the three parameters (page, search, page_size) beyond their self-explanatory names. Since schema description coverage is 0%, the description fails to compensate, leaving agents to guess at search semantics or default page sizes.

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 lists accessible Superset databases and includes their IDs, using a specific verb and resource. This distinguishes it from sibling tools like list_datasets or list_dashboards.

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 this tool is used when you need to see available databases, but it does not provide explicit guidance on when to prefer it over alternatives such as list_datasets, nor does it mention prerequisites or limitations.

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