wdata_run_sql

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

No annotations are provided, so description carries full burden. It transparently reveals the internal mechanics: creates a temporary saved query, runs it, downloads CSV, then deletes it. Discloses side effects and the lack of ad-hoc SQL endpoint. This is excellent behavioral transparency.

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 sentences: purpose, critical constraint, mechanics. Front-loaded, no fluff. Every sentence adds value.

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?

Covers purpose, table naming, dialect, and behavioral mechanics. Output schema documents return values, reducing need here. Could mention defaults for timeout/max_rows but not critical. Slightly incomplete for a 3-parameter tool with no schema descriptions.

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 has 0% description coverage, so description must compensate. It adds meaning for the 'sql' parameter by specifying required table reference format. However, 'timeout' and 'max_rows' are left unexplained, relying on their names. Partial compensation.

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?

Description clearly states 'Execute one-off Wdata SQL and return rows.' It uses specific verb+resource (run SQL) and distinguishes from sibling tools like wdata_run_saved_query by mentioning 'one-off' ad-hoc execution and referencing wdata_list_tables for table references.

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?

Provides clear context: when to use (one-off SQL), critical constraint (table naming via sql_ref), and dialect (Trino). Implicitly distinguishes from wdata_run_saved_query. Lacks an explicit 'when not to use' statement, but context is strong.

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