Adds N French business days to a date (?start=2026-07-13&add=30) or counts them over a range (?from=2026-07-01&to=2026-09-30). Skips weekends and the 11 French legal public holidays (movable feasts computed via Butcher-Meeus). mode=ouvres (Mon-Fri, default) or ouvrables (Mon-Sat). Deterministic local computation, JSON. Price: $0.005 USDC per call (x402).
| Name | Required | Description | Default |
|---|---|---|---|
| add | No | ||
| start | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully discloses behavior: skips weekends and 11 French holidays, uses Butcher-Meeus algorithm, supports two modes, deterministic local computation, returns JSON, and includes pricing. No contradictions.
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?
Two sentences: first explains core function with examples, second adds details on holidays, modes, computation, output, and pricing. Every sentence adds value; no wasted words.
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 purpose, parameters, behavior, modes, holidays, pricing, and output format (JSON). Without output schema, description does not detail exact return fields, but implies result (date or count) through examples. Almost 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 0%, so description compensates by explaining start as a date string and add as number of days. However, description mentions 'from' and 'to' parameters not present in schema, causing slight inconsistency.
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?
Description clearly states 'Adds N French business days to a date' and 'counts them over a range', specifying both verb and resource. It distinguishes from sibling tools which focus on company data and validation.
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 explicit usage examples with query parameters and explains two modes (ouvres/ouvrables). However, no explicit guidance on when not to use this tool or alternatives among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool serves a distinct verification or lookup purpose (e.g., company lookup, sanctions screening, address geocoding, IBAN validation) with no overlap. Even tools targeting the same source (e.g., check_eori vs. validate_vat_eu) have clearly different inputs and outputs.
Almost all tools follow a verb_noun pattern (verify, validate, lookup, check, find, screen) with clear nouns. The only exception is 'catalog' (a noun-only name), but it's a minor deviation that doesn't cause confusion.
19 tools is appropriate for a data verification service covering company data, sanctions, VAT, addresses, emails, IBANs, and financials. Each tool addresses a specific need without being excessive or sparse.
The tool set covers the full lifecycle of EU company verification: existence, status, financials, ownership, VAT, sanctions, EORI, invoices, tenders, and address validation. No obvious gaps for its stated domain.