regdata_spain_company_directory

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

No annotations are provided. The description mentions it is a scraper and that no API exists, but does not disclose behavioral traits such as rate limits, data freshness, error handling, or whether it is read-only. This limits the agent's ability to assess risks or side effects.

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 at a few sentences, front-loading the key purpose and data types. It avoids unnecessary details, though the reference to regdata_describe could be considered slightly extraneous given the simple input.

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 the tool's complexity as a scraper and the lack of an output schema, the description provides a reasonable list of output fields (NIF, officers, CNAE codes, etc.). However, it does not explain pagination, result limits (beyond maxItems), or error conditions. The reference to regdata_describe partially compensates for field ambiguity.

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 only one parameter (maxItems) and 100% schema description coverage, the schema already documents it adequately. The description adds minimal extra context (noting freeform input matches Apify schema), but does not enhance understanding beyond the schema definition.

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 states the tool's purpose: scrape company data from Spain's official Registro Mercantil, listing specific data points (NIF, officers, CNAE codes, etc.). It distinguishes from sibling tools by specifying the geographic source and data type, though it doesn't explicitly differentiate between similar country-specific scrapers.

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 advises calling regdata_describe for exact fields if unsure, which provides some guidance. However, it lacks explicit conditions for when to use versus alternative tools, and does not mention prerequisites or prohibited use cases.

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