get_company_by_siren

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

With no annotations, the description carries the behavioral burden. It describes a read-only operation returning specific data but does not disclose potential errors (e.g., SIREN not found), required permissions, rate limits, or side effects. It is not misleading but lacks completeness.

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 two sentences with no redundant information. It is front-loaded with the action and directly states what is returned, making it efficient and easy to parse.

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?

The tool has an output schema, so return values are covered. The description explains the purpose and main output but lacks mention of error handling (e.g., missing SIREN) or differentiation from similar tools. For a simple lookup, it is 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 100%, so baseline is 3. The tool description adds minimal value beyond the schema's parameter description, mainly restating the returned information. No additional semantics like example values or constraints beyond what schema provides.

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 action (look up), the resource (company in PPF directory), and the identifier (SIREN number). It also lists the returned information, making the purpose unambiguous and distinct from siblings like get_establishment_by_siret.

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 implies usage for exact SIREN lookup but does not explicitly state when to use this tool versus alternatives like search_company or get_establishment_by_siret. There is no guidance on prerequisites or scenarios where it would be inappropriate.

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