sql_get_query_plan

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns an 'estimated execution plan' and mentions it uses SET SHOWPLAN_ALL (implying read-only, non-executing behavior). However, it doesn't disclose that estimate is non-executed, output quirks, or that SHOWPLAN_ALL may be unsupported on some SQL dialects.

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, front-loaded with the core action, minimal waste. The parenthetical SET SHOWPLAN_ALL adds useful technical precision. Slightly more could be gained from elaboration, but this is appropriately tight.

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 one parameter, full schema coverage, no output schema, and no annotations, the description is reasonably complete for its simplicity. However, SHOWPLAN_ALL output format is complex text that could benefit from a hint about what the result looks like, and there's no note about non-execution of the query.

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% (the single 'sql' parameter is documented as 'The SELECT query to analyse'). The description reinforces the SELECT-only constraint but adds no meaning beyond the schema. Baseline 3 is appropriate given full schema coverage.

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?

States specific verb+resource: 'Get the estimated execution plan for a SELECT query as text'. The technical detail '(SET SHOWPLAN_ALL)' adds precision, and 'Useful for diagnosing slow queries' contextualizes it among sibling tools like sql_diagnose_issue and sql_run_query. Effectively distinguishes itself.

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?

Implies usage for slow query diagnosis ('Useful for diagnosing slow queries'), which distinguishes it from execution-focused tools like sql_run_query. However, no explicit exclusions or when-not-to-use guidance given, and no mention of how this compares to alternatives like sql_diagnose_issue.

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