regdata_societe_com

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool scrapes a free source with no API, but does not mention rate limits, data freshness, or potential scraping failures. The maxConcurrency parameter implies parallel scraping, but behavioral constraints like throttling are not addressed.

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 three sentences, each contributing unique information: the tool's purpose and data types, its source and richness, and extensibility via advanced fields. No wasted words, and the key information is front-loaded.

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 8 parameters with no required ones, full schema coverage, and no output schema, the description covers the tool's data sources and capabilities well. However, it does not describe the output format or provide an example, which would enhance completeness for an agent.

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 parameters are already well-documented. The description adds value by noting that advanced fields beyond the schema are accepted and listed by regdata_describe, but this is a minor addition. Baseline 3 is appropriate as the schema does the heavy lifting.

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 scrapes French company data from Societe.com, lists specific data types (directors, financials, shareholders, etc.), and distinguishes it from other country-specific sibling tools. It also notes it's the 'richest free French company data source with no API', reinforcing its unique purpose.

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 for French company data but does not explicitly state when to use this tool versus alternatives (e.g., when real-time data is needed or for specific jurisdictions). It lacks exclusions or when-not-to-use guidance, though the mention of advanced fields hints at consulting regdata_describe for extended capabilities.

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