regdata_societe_com

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

No annotations provided, so description must disclose behavioral traits. Mentions 'richest free source with no API' implying it's a scraper, but does not address rate limits, blocking risks, data freshness, or any side effects. Inadequate for a web scraper.

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?

Relatively concise: two sentences plus a brief note. Slight redundancy in first sentence (repeats 'France Societe.com Company Scraper' and 'Scrape French company data'). Still efficient.

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?

Covers core purpose and input preparation. Lacks output description, data limits, pagination, or behavioral notes. Adequate but incomplete for a scraper tool with no output schema.

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 has only maxItems with description. Description adds significant value by explaining the freeform search input (flat object with name, tax ID, etc.) and referencing regdata_describe for exact fields. Compensates for schema's generic additionalProperties.

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?

Clearly states the tool scrapes French company data from Societe.com, listing specific data types (directors, financials, etc.). Distinguishes it from sibling tools which target other countries or registries.

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?

Provides input format guidance (flat object with name, tax ID, etc.) and suggests calling regdata_describe if unsure of exact fields. Lacks explicit when-not-to-use or alternatives, but context is clear.

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