fluig_db_query

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

With no annotations, the description carries the full burden. It declares the tool is read-only (SELECT/WITH only) and mentions the result is temporary ('throwaway dataset'), but it does not disclose potential side effects, resource limits, or timeout behavior.

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 two concise sentences, front-loading the action and database, then clarifying scope. No extraneous words.

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?

Given the complexity of a dynamic SQL query tool, the description lacks details about return format, error handling, pagination, or any limits. However, the read-only safety is noted, and the context of available tables is helpful.

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% for the single parameter, which already repeats the constraint 'SELECT ... (SELECT/WITH only)'. The description adds minimal context (database scope, temporary dataset) but no additional format guidance or examples beyond the schema.

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 action ('Run a SELECT') and resource ('Fluig database through a throwaway dataset'), and it distinguishes itself from other database query tools (e.g., fluig_rm_db_query) by specifying 'any table' and giving examples of Fluig-specific tables.

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 the tool is for read-only SQL queries on the Fluig database, but it does not explicitly state when to use this tool versus alternatives like fluig_rm_db_query or the dataset tools. No exclusions or prerequisites are provided.

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