execute-batch-queries

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

Adds 'in parallel' which is a key behavioral trait. However, with no annotations, description fails to disclose error handling, transaction behavior, or result format. Partial credit for parallelism disclosure.

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?

Single sentence, no fluff. Perfectly concise and front-loaded with the action.

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?

Lacks critical context for a batch execution tool. No mention of output format, error handling, or transactionality. With no output schema, description should cover return behavior.

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 covers all parameters with descriptions (100% coverage). Description adds no additional meaning beyond summarizing the overall action. Baseline 3 is appropriate.

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?

Clearly states it executes multiple SQL queries in parallel. Distinguishes from sibling 'execute-query' which is for single queries. Verb 'executes' and resource 'batch queries' is specific.

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 explicit guidance on when to use vs alternatives. Only implies parallelism for performance, but does not mention when not to use or provide comparative context with sibling tools like 'execute-query'.

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