get_phones_bulk_result

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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds the context that this is a bulk result-retrieval operation, but it does not disclose relevant behavior such as whether results are available immediately, require polling, or may be partial if the bulk search is still running.

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, front-loaded sentence with no filler. Every word contributes to identifying the operation and resource.

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 is simple (one fully documented parameter, no nested objects) and the annotations cover safety, so the definition is minimally usable. However, there is no output schema and the description does not describe the shape of the returned results or the asynchronous relationship with find_phones_bulk, which are the main gaps.

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 100% and the single 'id' parameter is clearly documented as the batch ID returned by find_phones_bulk. The description itself adds no extra parameter semantics, but none are needed because the schema already carries the full meaning.

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 ('Retrieve') and a specific resource ('results of a bulk phone search'), clearly identifying this as the result-fetching counterpart to find_phones_bulk and distinguishing it from single-result get_phone_result. It states exactly what the tool does rather than merely repeating the name.

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 does not explicitly state when to use this tool versus alternatives. The parameter description ('Batch ID returned from find_phones_bulk') implies that the agent should call find_phones_bulk first, but this is in the schema, not the description, and there is no guidance about polling or choosing between get_phone_result and this tool.

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