get_company_by_id_instance

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

No annotations provided, so description carries full burden. It only states 'look up', which implies read-only, but no details on prerequisites, failure modes, or other behavioral traits. Minimal but sufficient for a simple 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?

Single sentence with exactly 12 words. No fluff, front-loaded with purpose, and includes the endpoint for developer reference. Efficient and well-structured.

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?

Given the tool's simplicity (one parameter, output schema present), the description is complete enough. It specifies the identifier type and action. Minor improvement could mention its use after a search, but not required.

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 parameter is already described in the schema. The description adds no additional meaning beyond restating the parameter's purpose, meeting the baseline.

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 a legal unit' and specifies the unique identifier type 'directory instance ID'. It includes the exact GET endpoint, making the purpose unambiguous. It distinguishes from siblings that use different identifiers (SIREN, 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?

No explicit guidance on when to use this tool versus alternatives like get_company_by_siren or get_establishment_by_id_instance. The parameter description hints at 'from a previous search', but the main description lacks usage context.

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