regdata_spain_company_directory

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

With no annotations provided, the description must disclose behavioral traits. It indicates the tool is a scraper but does not mention read-only status, rate limits, data freshness, or potential side effects. The description is too minimal for a scraping tool.

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 concise (3 sentences) with no superfluous content. It front-loads the tool name and purpose, followed by acceptable parameters and a reference to another tool. Every 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?

The description lists data fields returned but lacks details on the output format or pagination behavior. Given no output schema and 7 parameters, more detail on how results are structured would improve completeness, though the reference to regdata_describe partially compensates.

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?

Input schema coverage is 100% with each parameter described. The description adds value by noting that advanced fields beyond the schema are accepted and directing users to regdata_describe for details, which enhances understanding 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 clearly specifies the tool's purpose: scraping Spain's official company directory (Registro Mercantil) and listing the specific data fields (NIF, officers, CNAE codes, etc.). It differentiates from siblings by targeting Spain and referencing regdata_describe for advanced fields.

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 mentions that no API exists for this data, implying this tool is the only means, but it does not explicitly state when to use this tool over alternatives like regdata_spain_concursal or other country-specific tools. No exclusion criteria or alternatives are given.

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