regdata_italy_pec

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

Without annotations, description adds value by disclosing 'No official API' and that advanced fields are accepted. It doesn't discuss side effects, but as a read-like lookup, the transparency is adequate.

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: first defines purpose, second lists use cases, third notes schema extensibility. No wasted words, front-loaded with key info.

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?

No output schema, but description specifies key outputs (PEC email, SDI code) and result structure. It also mentions advanced fields via another tool. Sufficient for a lookup tool.

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, description still adds meaning: clarifies identifier types (VAT, CF, name) and output behavior ('One result row per identifier'). It also references 'regdata_describe' for advanced fields, enriching schema info.

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 clearly states the tool resolves Italian PEC email and SDI code from VAT, tax code, or company name. It distinguishes from siblings like 'regdata_italy_registro_imprese' by focusing on PEC/SDI lookups.

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?

Description mentions use cases: e-invoicing, KYC, bulk enrichment. It implies when to use (for Italian company digital data) but does not explicitly state when not to use or suggest alternatives.

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