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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no result count limits, no pagination behavior, no note that the corpus is limited to French companies (that appears only in the title), and no rate/quota statement beyond the word 'Free'.

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 short sentence with the identifiers front-loaded and no padding. It is efficient, though the terseness borders on under-specification for a search tool with pagination.

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?

With no annotations and no output schema, the description should explain at least the result shape and page semantics; neither is covered. The agent knows what to pass but not what it will get back.

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 50% and the covered half (query) already documents that name, SIREN, SIRET or activity are accepted, so the description largely repeats it. The page parameter is undocumented in both the schema and the description, leaving a real gap.

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 ('Finds') and resource ('companies'), plus the key identifiers accepted. It doesn't explicitly contrast with the sibling get_company, which retrieves a single company, so the search-vs-lookup distinction is left implicit.

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?

There is no guidance on when to use this instead of get_company, or what to do once a SIREN is known. 'Free' hints at a cost dimension but does not tell the agent anything about selection.

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