bulk_validate_aadhaar

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds value by mentioning ThreadPoolExecutor for parallel processing. It does not detail concurrency limits, error handling, or rate limits, but these are not critical given the annotations.

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?

Two concise sentences with no redundant information. The first sentence front-loads the action and key detail (parallel execution). Efficient and to the point.

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 existence of an output schema (no need to describe returns), annotations for safety/idempotence, and the description covering purpose, usage, and parallelization, the tool is adequately specified. Minor gap: no mention of validation criteria or error 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 coverage is 100% with the 'numbers' parameter description including max 500 limit. The description adds no parameter-specific details beyond what the schema provides, so 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?

Description uses specific verb 'Validate' with resource 'multiple Aadhaar numbers' and mentions parallel execution via ThreadPoolExecutor, clearly distinguishing from sibling validate_aadhaar which handles single numbers.

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?

Explicitly states batch validation for KYC, onboarding, or compliance workflows, implying it is not for single validation. However, it does not explicitly mention the alternative sibling tool validate_aadhaar for single cases.

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