query_sql

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

With no annotations, the description carries the full burden. It discloses read-only behavior, statement type restrictions, and row capping. While it could mention error handling or auth needs, the current disclosure is above average for a simple SQL tool.

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?

Three short sentences, front-loaded with the main purpose. Every sentence adds value without redundancy. Highly efficient and easy to parse.

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 tool with one parameter and no output schema, the description covers input constraints, usage context, and a prerequisite sibling. It hints at the output (tabular result) but could specify the row cap value or clarify pagination. Still, it's largely complete for typical use.

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 single parameter 'sql' has 0% schematic description coverage, so the description must compensate. It clarifies allowed SQL constructs (SELECT/WITH) and implies a row limit, but lacks syntax examples or format details. This is adequate but not exceptional.

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 runs a 'read-only SELECT' against the 'mart,' specifying the verb and resource. It distinguishes itself from sibling tools like 'describe_schema' and 'list_datasets' by focusing on querying rather than metadata or analysis.

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 explicit when-to-use guidance ('Run a read-only SELECT'), what is not allowed ('Only single SELECT / WITH statements'), and a key alternative ('Use describe_schema to learn column names before querying'). This helps the agent choose correctly.

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