list_running_queries

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

No annotations exist, so description carries full burden. It states the tool returns currently-executing queries, implying a read operation, but does not disclose potential limitations (e.g., pagination, permission requirements, result size). Minimal additional behavioral context beyond the obvious.

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?

Description is concise, with a clear one-line summary and an argument list. No redundant sentences. Could be slightly more streamlined (e.g., remove 'Args' formatting), but structure is effective and front-loaded with the main action.

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?

Given that an output schema exists (not shown), the description adequately covers the tool's purpose and inputs. It could mention what fields are returned (e.g., query ID, status), but overall it's complete for a straightforward list tool. No critical omissions.

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?

Input schema has 0% description coverage (no schema descriptions). Description adds meaning by specifying each parameter: 'Workspace name or GUID' and 'Item: Warehouse or SQL Analytics Endpoint name or GUID.' This compensates for missing schema descriptions, providing necessary semantic context.

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 the tool returns all currently-executing queries on a specific warehouse or SQL Analytics Endpoint. Verb 'Return' and resource 'currently-executing queries' are unambiguous. Distinguishes from siblings like list_long_running_queries and list_frequent_queries by focusing on active queries.

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 explicit guidance on when to use this tool versus alternatives (e.g., list_long_running_queries for long-running queries). No prerequisites or scenarios provided. Description implies usage context (fetching active queries) but lacks comparative guidance.

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