Fiche publique d’une entreprise

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

No annotations, so the description carries the full burden. It usefully discloses the returned content areas (including a dated headcount range and 'finances disponibles', hinting at conditionally-present data), but omits permission/auth requirements, whether some fields may be absent, and any response-shape detail.

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?

A single front-loaded sentence with zero waste; the verb+resource+payload lead immediately.

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?

For a simple one-parameter lookup with no output schema, the description adequately frames what comes back, but the absence of usage routing, SIREN format guidance, and partial-data behavior leaves clear gaps.

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 coverage is 0% and the single siren parameter has no schema description. The description adds that the lookup key is a SIREN, which is meaningful, but gives no format, validation, or example detail to compensate for the empty 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?

States a specific verb (Récupère) and resource (fiche publique) and enumerates the returned data sections (identité, siège, activité, effectif datée, dirigeants, finances). This lets an agent distinguish it from a bare resolver, though it doesn't explicitly differentiate itself from siblings like resolve_company or triage_company.

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?

Says nothing about when to use this tool versus the many sibling company tools, nor any prerequisites. Usage is only implied by the single SIREN input.

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