explain_plan

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the tool returns output but does not mention that it is read-only, does not execute the query, or any prerequisites like required privileges. This lack of detail could mislead an agent into thinking the query is run or that it has side effects.

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 a single sentence that conveys the essential purpose without any fluff. It is front-loaded with the key information. Every word earns its place.

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 has one parameter and an output schema exists, the description is still too minimal. It lacks usage guidelines, behavioral transparency, and any context about prerequisites or side effects. For an agent to use it correctly, more information is needed.

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?

The input schema has 0% description coverage, so the description must compensate. It adds that the 'sql' parameter must be a SELECT query, which is not indicated in the schema. However, it does not specify format, syntax rules, or restrictions (e.g., no DDL). This is minimal added value.

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 returns Oracle EXPLAIN PLAN output for a SELECT query. The verb 'Return' and resource 'Oracle EXPLAIN PLAN output' are specific. It distinguishes itself from sibling tools like 'run_select' (which executes the query) and 'top_sql' (which lists top SQL).

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 does not explicitly state when to use this tool versus alternatives. While it implies use for analyzing query execution plans without running the query, no when-not or alternative tools are mentioned. The guidance is adequate but not explicit.

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