regdata_italy_registro_imprese

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

No annotations are present, so the description bears full responsibility. It discloses that the tool is a scraper without an official API ('No official API - structured JSON') and mentions that advanced fields are accepted, but it omits details on rate limits, error handling, data freshness, or what happens when a company is not found.

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 two sentences with an additional note, all front-loaded with the core purpose. No extraneous words; every sentence adds necessary context.

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?

The tool is a scraper with no output schema or annotations. The description lists returned fields and indicates JSON output, but does not specify response structure, pagination, or error behavior. For a simple data retrieval tool, it covers the essentials but could be more complete.

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 description coverage is 100%, so the schema itself documents all parameters. The description adds value by noting that 'Advanced fields beyond this schema are also accepted (regdata_describe lists them)', but does not elaborate on param usage beyond the schema.

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 is an Italy Registro Imprese scraper, specifies the search method (by company name), and lists the data fields extracted (name, registered office, PEC, legal form, ATECO, business description). It clearly distinguishes itself from sibling tools through the name and registry specificity.

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?

The description implies usage when an Italian company name or VAT is available, but does not explicitly state when to use this tool versus alternatives like regdata_italy_pec or other country-specific tools. No guidance on when not to use it, prerequisites, or limitations is provided.

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