sql_Execute_Full_Pipeline

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

The description implies write operations (e.g., 'Creates vector store', 'Creates cluster statistics'), but annotations set readOnlyHint: true and idempotentHint: true. This is a direct contradiction. The description does not disclose that the tool writes to the database, despite mentioning sufficient space in feature_ext_db.

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 long but well-structured with sections, bold headers, and bullet points. It front-loads the purpose and workflow. Some redundancy could be trimmed, but overall it's organized for readability.

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 complexity (multi-step pipeline), minimal input schema, and no output schema, the description provides extensive context: full workflow steps, performance metrics explanations, configuration details, prerequisites, and follow-up tools. It is highly complete.

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, but the description explains that optimal_k controls the number of clusters and max_queries limits the top queries by CPU time. It provides meaning beyond the schema's raw parameter definitions.

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 that the tool 'executes the entire SQL query clustering workflow' to identify high CPU usage queries. It distinguishes itself from siblings by detailing the full pipeline and referencing subsequent tools like sql_Analyze_Cluster_Stats and sql_Retrieve_Cluster_Queries as follow-ups.

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 includes an 'OPTIMIZATION WORKFLOW' section that explicitly tells when to use this tool and what tools to use after (e.g., sql_Analyze_Cluster_Stats). It also lists use cases and prerequisites, providing clear guidance on appropriate usage.

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