partition_pruning_check

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

No annotations are provided, so the description carries full burden. It only states the tool is read-only, but does not disclose potential costs, side effects, or the nature of the heuristic analysis. The agent cannot gauge whether this tool is safe or costly.

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, clear sentence with no unnecessary words. It front-loads the key action (EXPLAIN) and purpose (assess partition pruning).

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 no annotations and an output schema, the description still lacks completeness. It does not explain what the output contains, how the heuristic works, or any limitations. For a diagnostic tool, more context is needed to enable correct use.

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?

With 0% schema description coverage, the description must compensate. It adds that the 'query' parameter should be a read-only SQL query, which is more informative than the schema's plain string type. However, it could be more precise (e.g., 'SELECT statement' or required format).

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's purpose: 'EXPLAIN a read-only query and heuristically assess whether partition pruning is likely.' It uses a specific verb and resource, and distinguishes it from sibling tools like 'explain_query' (which likely does generic explain) and 'hot_partitions' (which checks current partitions).

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?

No guidance is provided on when to use this tool versus alternatives like 'explain_query' or 'hot_partitions'. The description does not mention prerequisites, compatible query types, or when the heuristic assessment is reliable.

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