bulk_validate_aadhaar

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

Annotations already declare readOnlyHint and idempotentHint, and the description adds genuinely useful behavioral details: parallel execution via ThreadPoolExecutor, a 500-item cap, per-Aadhaar results with counts, and consistency with the single-tool Verhoeff algorithm. No contradiction with 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?

The description is well organized with clearly labeled sections: usage, args, returns, and notes. Every sentence earns its place, and the main purpose is front-loaded before implementation details.

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 only one parameter, a rich output schema, and annotations covering safety, the description provides everything needed: when to use it, input normalization, batch limit, parallelism, and return behavior. Nothing important is missing.

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 schema covers the parameter at 100%, but the description adds meaningful input semantics beyond the schema by stating that numbers may include spaces or hyphens and reinforcing the max-500 list constraint. This helps the agent prepare valid input.

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?

States a specific verb and resource: validate multiple Aadhaar numbers. The description adds parallel execution detail, and the word 'multiple' plus batch focus clearly distinguishes it from validate_aadhaar.

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 says to use when batch-validating for KYC, onboarding, or compliance workflows, which gives clear context. It does not explicitly name validate_aadhaar as the single-item alternative, so it falls just short of full when-not/alternatives guidance.

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