validate_partita_iva

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

The description details the validation algorithm, whitespace stripping, and the exact return format for both success and failure cases. No annotations exist, so the description fully covers behavior.

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-structured with the main purpose first, then usage, algorithm, and return format. Slightly long due to algorithm details, but each sentence adds value.

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 one parameter, the description fully covers behavior, output, and usage context. The algorithm details ensure completeness, though it could mention the sibling validate_partita_iva_format.

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?

With 100% schema coverage, baseline is 3. The description adds algorithm details and return structure beyond the schema's format constraint, justifying a 4.

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 explicitly states the tool validates an Italian Partita IVA for format (11 digits) and modulo-10 checksum, distinguishing it from sibling tools like validate_cedente_prestatore and validate_partita_iva_format.

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 advises calling this as an early sanity check before using validate_cedente_prestatore(), providing clear when-to-use guidance and differentiation from a related tool.

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