explain_analyze

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

There are no annotations, so the description carries the full behavioral burden. It does disclose that the tool uses EXPLAIN ANALYZE and reports costs, which is meaningful. However, it does not warn that EXPLAIN ANALYZE actually executes the query, which could be important for safety and 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 front-loaded sentence with no redundancy or filler. It states the purpose and mechanism in the fewest words needed.

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?

The output schema and parameter schema cover return values and arguments, which reduces the burden on the description. Still, the description lacks explicit when-to-use guidance and any caveat about EXPLAIN ANALYZE executing the query, so it is not fully complete for safe and correct invocation.

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 both sql and params are already well documented in the input schema. The description adds no extra parameter-level meaning beyond restating that the query will be analyzed, so the baseline of 3 applies.

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 states a specific verb ('Get'), a concrete resource ('query execution plan with costs'), and the mechanism ('EXPLAIN ANALYZE'). This clearly distinguishes it from sibling tools like query and execute, which return results rather than plans.

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 implies this tool is for performance analysis and execution plans, not for retrieving query results. However, it never explicitly says when to choose this over query or execute, and it gives no exclusions or alternative guidance.

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