infoset_batch_get_contacts

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

With no annotations, the description carries the transparency burden. It discloses the non-obvious auto-deduplication behavior, which is valuable. But it doesn't clarify what happens with invalid IDs, whether order is preserved, or how partial failures are handled.

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, focused sentence delivers the essential information with no redundancy. It is front-loaded 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?

For a simple one-parameter batch tool with no output schema, the description covers the core purpose and one key behavior. It is sufficient for an agent to select and invoke the tool, though it could mention response format or error handling for full completeness.

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 fully documents contactIds as an array of numbers. The description adds behavioral meaning by noting auto-deduplication, which tells the agent that duplicate IDs are acceptable and will be handled—value beyond the schema.

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 uses a specific verb-resource pair ('Get multiple Infoset contacts') and adds scope 'in a single call', clearly distinguishing it from the singular get_contact tool. The auto-deduplicates note further refines its purpose.

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 phrase 'in a single call' implies the intended use case—fetching multiple contacts efficiently—which differentiates it from repeatedly calling get_contact. However, it doesn't explicitly state when not to use it or mention alternatives like list_contacts.

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