infoset_batch_get_companies

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

The description discloses the auto-deduplication behavior, which is beyond the tool's name and adds some behavioral insight. However, with no annotations, it does not address error handling, limits, or response structure, leaving significant behavioral aspects undisclosed.

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 a single concise sentence that front-loads the core purpose and includes a useful parenthetical about deduplication. There is no wasted wording.

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 simple one-parameter batch read, the description explains the core behavior but omits potential limits, error behavior, and how to use it relative to similar single-item tools. This leaves some gaps in context.

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 schema provides a complete description of the companyIds parameter (array of company IDs), and the tool description does not add additional parameter-specific semantics beyond 'auto-deduplicates,' which implicitly relates to how IDs are processed. With 100% schema coverage, the baseline of 3 is applied.

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 multiple Infoset companies in a single call, using 'get' as the verb and naming the resource. The mention of 'multiple' and 'single call' distinguishes it from the sibling infoset_get_company (singular).

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 the tool is for fetching several companies at once rather than individually, but it does not explicitly reference when to prefer it over alternatives like infoset_get_company or infoset_batch_get_tickets. There is no explicit when-not or alternative guidance, so usage is only implied.

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