explain

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It names the output as a query plan and the purpose as analysis, implying read-only behavior, but it does not explicitly state that the query is not executed or describe any output format/limitations.

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, tightly worded sentence with no filler. It front-loads the core action and immediately explains the tool's practical value.

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 an output schema present and complete parameter documentation, the description covers the essential context. A slight gap is the absence of an explicit note that this tool analyzes rather than executes the query, which would further differentiate it from the query sibling.

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 all three parameters (db, sql, params). The description adds no extra parameter-level detail, but this is acceptable given the strong 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?

The description uses a specific verb and resource ('Explain the query plan for a SQL query') and explicitly names the underlying SQLite command (EXPLAIN QUERY PLAN). It clearly distinguishes itself from siblings like query, which executes queries, and schema/table_info, which inspect 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 communicates clear context for use: analyzing indexes and optimizing query performance. It does not explicitly name sibling alternatives or state when not to use the tool, but the stated purpose is sufficient to guide selection among the listed siblings.

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