Get a company profile by SIREN or SIRET

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

With no annotations provided, the description carries the behavioral disclosure burden. It goes beyond a simple 'get' by listing the returned fields and, notably, explaining the `missing` array and warning not to fabricate missing data — important behavioral guidance. It could mention error handling or data freshness, but it is still substantially transparent for a read-only lookup.

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, with the core purpose stated first and the important `missing`-array caveat in the second sentence. Every sentence adds value and there is no redundant or filler text.

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 single-parameter lookup tool with no output schema, the description is complete: it explains what is returned, mentions the caveat about missing fields, and gives the identifier formats. The agent has enough context to call the tool correctly and interpret the response.

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 the schema already fully documents the `identifier` parameter including formats and space tolerance. The tool description does not add parameter-level detail beyond that, so the baseline score of 3 is appropriate.

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 retrieves a 'full profile for one company' by SIREN or SIRET, naming the returned data categories (legal form, activity, workforce, etc.). This distinguishes it from the sibling tools, especially search_companies, by emphasizing lookup by unique identifier rather than search.

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 makes the intended usage context clear: use this when you have a SIREN or SIRET and need a single company's full profile. It does not explicitly exclude the sibling tools or state when to prefer search_companies, but the identifier-based lookup is strongly implied.

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