get_emails_bulk_result

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

The readOnlyHint and openWorldHint annotations already convey that this is a safe read operation, and the description merely restates 'retrieve.' Nothing is disclosed about asynchronous bulk-job semantics, whether results can be fetched more than once, or how the result payload is structured.

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. It states the core operation immediately and does not waste tokens.

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 one-parameter, read-only retrieval tool with full schema coverage, the description is minimally adequate. The lack of an output schema means the description could have usefully explained what a bulk email search result looks like, but it does not; it also omits any polling or availability caveats.

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 id parameter is documented as the batch ID returned from find_emails_bulk, so the schema carries the parameter meaning. The tool description adds no independent parameter guidance, which is acceptable given the full schema coverage.

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 identifies the action (Retrieve) and the resource (results of a bulk email search), which distinguishes it from singular/verification siblings. However, it largely paraphrases the tool name and title without adding operational specifics such as what the returned results contain.

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 'bulk email search' implies this tool is used after starting a bulk search, but the description never explicitly says to use it with the ID from find_emails_bulk or mentions alternatives like get_email_result for single searches. The only concrete pairing hint lives in the schema's id description, not in the tool description.

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