get_all_dbs

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

No annotations provided, so description carries full burden. It discloses the return type (TaosSqlResponse) and scope (current Taos configuration). However, it fails to mention read-only safety, error conditions (e.g., connection failures), or side effects, which are critical for a database tool without annotation hints.

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?

Brief and mostly front-loaded with the Returns section providing structured output documentation. Slightly odd indentation in the Returns block, but generally efficient with no redundant sentences. Could be more compact.

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?

Appropriate for a zero-parameter listing tool where output schema exists (per context signals). The description mentions TaosSqlResponse, complementing the structured output schema. Missing guidance on the sibling tool ecosystem prevents a higher score.

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?

Zero parameters present. Per scoring rules, 0 params = baseline 4. The description mentions 'current Taos configuration' implying context-dependency, but does not explicitly document why no parameters are needed or what context is used.

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 specific action (Get) and resource (databases), expanding 'dbs' from the name. Mentions 'current Taos configuration' which provides useful scope context. However, it does not explicitly differentiate from siblings like get_all_stables (which gets super tables) or query_taos_db_data (which queries data).

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?

Provides no guidance on when to use this versus alternatives like switch_db (which changes context) or query_taos_db_data (which queries contents). No prerequisites or error conditions mentioned despite the implicit dependency on current Taos configuration context.

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