Explain query execution plan

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

Annotations provide no safety hints (all false), so the description carries the burden. It reveals that only SELECT/WITH are accepted and that the result is an operator tree from EXPLAIN_PLAN_TABLE, which is useful. However, it does not explicitly state that the tool is read-only, mention required privileges, or describe error behavior, leaving room for more disclosure.

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?

The description is two sentences long, front-loads the core action, and includes a concise constraint. Every word adds value with no redundancy or fluff, making it highly efficient.

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 tool's simplicity (one parameter, no output schema), the description provides adequate context: what it does, what input is allowed, and what output to expect. It could mention limitations or prerequisites (e.g., whether special permissions are needed), but the current level is sufficient for most use cases.

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 description coverage is 100%, so the schema already documents the 'query' parameter fully. The description adds no new semantic detail beyond what the schema provides, only restating the SELECT/WITH restriction. Thus, a 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 a specific action ('Run EXPLAIN PLAN') on a specific resource (a SELECT/WITH query) and specifies the output ('operator tree from EXPLAIN_PLAN_TABLE'). It also distinguishes from sibling tools like hana_explain_table by focusing on query execution plans rather than table structure.

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 provides clear context for when to use the tool (to explain a SELECT/WITH query) and an explicit exclusion ('Only SELECT/WITH are accepted'). However, it does not explicitly mention alternatives or contrast with sibling tools, so it falls short of full usage guidance.

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