get_query_plan

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

Explains key behavioral traits: no execution, read-only safety, returns SHOWPLAN_XML, and supports both Warehouse and SQL Analytics Endpoint items. However, it lacks details about error handling or limitations like query size.

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?

Well-structured and concise: a one-sentence purpose, then paragraphs on safety, plan XML details, args, and return value. No extraneous content; front-loaded with key information.

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 the 3 simple parameters and existence of output schema, the description covers purpose, safety, output format, and supported items. Minor gaps like error handling but overall adequate.

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?

With 0% schema description coverage, the description includes an Args section that briefly describes each parameter (workspace, item, query), adding basic meaning but lacking format details or examples.

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 captures an estimated execution plan without executing the query, using specific verbs ('Capture', 'retrieves') and distinguishes it from similar tools that execute 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?

Explicitly states that the tool does NOT execute the query and is safe to use even under read-only mode, providing clear guidance on when to use it (for plan analysis) vs. alternatives like execute_sql.

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