base_databaseList

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

No annotations are available, so the description carries full burden. It reveals that 'persist' materializes results as a volatile table, which is a useful behavioral detail. However, it does not mention whether the operation is read-only, required permissions, or rate limits, leaving some behavioral gaps.

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 concise (two short paragraphs) and front-loaded with the primary purpose. The structured bullet list of arguments is clear and easy to parse. Minor improvement: could be even more succinct.

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 simple listing tool with only two parameters and no output schema, the description adequately covers purpose and parameter behavior. It does not explain return format beyond the persist option, but given the tool's simplicity, it is sufficiently complete.

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 100%, and the description's parameter explanations closely mirror the schema's descriptions, adding no new semantic value. 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?

The description clearly states the tool's action ('Lists databases') and resource ('Teradata System'), with added specificity about scope filtering. It distinguishes itself from sibling list tools like base_tableList by focusing on databases, ensuring the agent understands it is for database-level listing.

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 provides clear guidance on the two scope options ('user' vs 'all') and the persist parameter, helping the agent choose the right configuration. However, it does not explicitly state when to use this tool over alternatives like base_tableList, relying on the tool name and context.

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