find_phones_bulk

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

The description discloses a key behavioral trait beyond the annotations: the operation is asynchronous and returns a batch id rather than immediate results. This is essential for an agent to invoke and handle the tool correctly. It also communicates the batch size limit. Annotations are not contradicted; readOnlyHint=false is consistent with creating a batch job.

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?

Two concise sentences with no filler. The first sentence gives the core action and batch limit; the second explains the async flow and points to the poll endpoint. All information is front-loaded and directly useful.

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 tool with one parameter, a straightforward schema, and no output schema, the description covers the essential operational details: bulk limit, async behavior, and the complementary polling tool. It does not describe potential errors or result structure, but those are not strictly necessary here, given the schema and sibling tools. Overall adequate and complete for invocation.

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 coverage is 100%—the only parameter 'searches' is described as an array of search objects with max 3,000. The tool description repeats the batch limit but does not add deeper semantics about the inner fields (last_name, first_name, etc.). With high schema coverage, baseline 3 is appropriate, and the description offers no extra parameter-level detail.

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 ('Find multiple phone numbers in bulk'), the resource ('phone numbers'), and the batch limit (up to 3,000 per batch). It also distinguishes itself from siblings like find_phone (singular) and get_phones_bulk_result (result polling) by explicitly framing this as the bulk lookup operation.

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 a clear usage flow: it is asynchronous, returns a batch id, and requires polling get_phones_bulk_result. While it does not explicitly mention when not to use it (e.g., for single lookups use find_phone), the bulk context and sibling names make this fairly obvious. Slight gap remains in explicit exclusion guidance.

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