anaf_company_lookup_batch

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

With no annotations, the description carries the behavioral burden and does well by explaining that unmatched CUIs are omitted rather than treated as errors. It also conveys a read-only lookup nature and batch-size limit. It could add details like request-size consequences or authentication, but the core behavior is transparent.

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?

Three sentences, each earning its place: what it does, when to prefer it, and the key edge-case behavior. No filler or redundancy.

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 fields are covered, and the description provides essential lookup context, batch limits, and missing-record behavior. The main gap is the undocumented as_of parameter, which prevents full call readiness.

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?

The description clarifies the cuis parameter ('by CUI', 'multiple Romanian companies') despite 0% schema coverage. However, the as_of parameter is not explained at all, including its format, purpose, or default behavior.

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 states a specific action ('Look up multiple Romanian companies by CUI in one call'), a clear resource scope, and differentiates itself from the sibling anaf_company_lookup. Saying 'Same per-company fields as anaf_company_lookup' reinforces what the tool returns without ambiguity.

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?

Explicitly instructs when to prefer this tool: batch up to 100 CUIs in a single request instead of calling anaf_company_lookup repeatedly. This gives the agent a direct decision rule for tool selection.

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