execute_async_query

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

The description notes the tool is asynchronous and returns a query ID, but with no annotations, it fails to explain that results must be retrieved later (e.g., via get_query_results), potential failure modes, or that the query is queued. This is a significant omission for an async 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?

Two sentences with no wasted words: the first states the core purpose and context, the second specifies the return value. Perfectly front-loaded and concise.

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 tool has asynchronous behavior requiring subsequent polling to retrieve results, but the description omits this crucial workflow. It also lacks any explanation of error handling or timeouts beyond the parameter. Given the complexity and no output schema, the description is incomplete.

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% and the schema already describes both parameters adequately. The description adds no additional meaning beyond restating the schema descriptions, so baseline score of 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 states the action ('execute'), the resource ('asynchronous SQL query'), and the context ('for large datasets or long-running queries'), and distinguishes from siblings like execute_sql_query (presumably synchronous) by specifying it returns a query ID.

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 indicates when to use this tool ('for large datasets or long-running queries'), implying an alternative is the synchronous query tool. While it doesn't explicitly list alternatives or when-not-to-use, the context of sibling tools provides sufficient guidance.

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