bulk_validate_gstin

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

The description explains the parallel execution via ThreadPoolExecutor and performance improvement to ~N/10 batches, adding context beyond annotations (readOnlyHint, idempotentHint). No destructive behavior is indicated.

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?

Three concise sentences, each adding distinct value: action, usage guidance, and performance benefit. No wasted words.

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 one parameter, annotations, and existing output schema, the description covers purpose, usage, and performance. It is complete for the tool's complexity, though output details are left to the schema.

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 coverage is 100% with the parameter description 'List of GSTINs to validate (max 500)'. The description adds no further parameter information; baseline of 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?

The description clearly states the tool validates multiple GSTINs in parallel, distinguishing it from sibling tools like 'validate_gstin' and other bulk validators by specifying the resource and parallel execution.

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?

It explicitly gives usage context: 'Use when batch-validating vendor GSTINs for onboarding or reconciliation.' This helps in selecting the tool over alternatives, though it doesn't explicitly mention when not to use it.

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