get_contacts_by_ids

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds useful constraints (max 30 IDs, comma-separated format) but does not disclose behavior for invalid IDs, partial successes, or limits exceeded. Some behavior is inferable from 'standard contact listings', but error handling and edge cases are absent.

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 extremely concise, with a front-loaded declarative sentence and a minimal args section. Every word earns its place; no fluff or repetition.

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 getter with an output schema present, the description covers the essential constraints (count limit, input format). It lacks nuance about failure modes or alternatives, but given the tool's simplicity and available output schema, it is reasonably 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 0%, so the description must compensate. It does so by explaining contact_ids as 'Comma-separated contact IDs (max 30)', which adds format and limit semantics beyond the bare schema type 'string'. This fully documents the only parameter.

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's function with a specific verb ('Return'), resource ('contact listings'), and scope ('up to 30 explicit IDs'). It distinguishes itself from siblings like get_contact (single ID) and search_contacts (query-based) by emphasizing explicit IDs and batch handling.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention any exclusions (e.g., 'use get_contact for a single contact') or context for choosing it over list_contacts or search_contacts. The usage is only implied by the tool name and args.

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