sql_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does state that the tool is read-only and only supports SELECT/WITH, which signals no data mutation. It does not mention output details or error behavior, but the output schema covers return structure.

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 a single sentence with no filler, and it front-loads the most important constraint: read-only SQL query restricted to SELECT/WITH. Every word adds meaningful information.

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 core query behavior and safety constraint are present, and an output schema exists, so return values do not need explanation. However, the semantics of format and source parameters are missing, and there is no explicit guidance on when this tool should be preferred over sibling query 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 description coverage is 0%, so the description should compensate for undocumented parameters, but it does not explain sql, format, or source beyond implying SQL execution targets. The execution-target hint is weakly relevant to the source parameter, but the format parameter remains entirely unexplained.

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 identifies the tool as a read-only SQL query limited to SELECT/WITH and states that it runs on SQLite or DataFrames. It is specific about the verb and resource, though it does not explicitly differentiate itself from sibling tools like query_video_stats.

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 usage context by restricting queries to read-only SELECT/WITH statements, implying that write or non-query operations should not be attempted. It does not name alternative tools or provide explicit when-not scenarios beyond the read-only restriction.

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