query

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

No annotations are provided, so the description carries the full burden of disclosing behavior. It states that SQL is executed and results are returned, but it does not say whether this is read-only, whether DDL/DML is permitted, whether side effects can occur, or what happens if the query is expensive or large. This is a significant gap for an arbitrary SQL execution 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?

The description is a single, direct sentence that front-loads the action and result. There is no wasted wording or redundant detail.

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?

With no annotations and no output schema, the description needs to provide enough context for an agent to invoke the tool safely and correctly. For an arbitrary SQL execution tool, it omits important constraints: whether only SELECT is allowed, how results are returned, row limits, and potential cost or side-effect warnings. The description is minimally functional but not complete for this kind of operation.

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 input schema already documents the single 'sql' parameter with 100% coverage. The description essentially restates the schema field ('BigQuery sql statement'), adding little meaning beyond what the structured definition provides. Baseline 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 identifies the action ('Executes'), the resource ('BigQuery sql statement'), and the outcome ('returns the results'). It is unambiguous, though it does not explicitly differentiate itself from sibling tools list_tables and get_schema, which are also BigQuery-related.

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?

No guidance is given about when to use this tool versus list_tables or get_schema. An agent is not told that query should be used for arbitrary SQL while the siblings cover metadata or schema access, nor are any exclusions or prerequisites stated.

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