bulk_validate_pan

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

Annotations already declare readOnly and idempotent hints, so the description's main added behavior is the 'in parallel' execution trait, which is meaningful for understanding concurrency/review implications. The '# PermissionTier' tag slightly reinforces the read-only nature but mostly duplicates the annotation.

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?

One short active sentence plus a metadata tag, with no filler. The verb and resource are front-loaded, and every token earns its place.

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 a single simple parameter, rich schema coverage, an output schema, and annotations covering safety and idempotency, the description provides all needed context. Nothing essential 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 description covers 100% of parameter semantics, including 'List of PANs to validate (max 500)'. The tool description adds no further parameter depth, 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 states a specific verb ('Validate'), a concrete resource ('multiple PANs'), and a behavioral nuance ('in parallel'). This unambiguously distinguishes it from single-item siblings like validate_pan.

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?

Implied usage context is clear: use this when validating multiple PANs in parallel, contrasting with single-PAN tools. However, it does not explicitly name the alternative or state 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.