get_bulk_item_result

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

Beyond the readOnlyHint/openWorldHint/destructiveHint annotations, the description discloses important behaviors: results expire after 24 hours, an expired item returns a clear message, and the tool is free of per-call credits. It also explains that the returned data varies by job operation, adding context the annotations do not capture.

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 front-loaded with the main purpose and organized into clear usage and expiration sections. It is somewhat longer than strictly necessary for a one-parameter tool, but each sentence contributes meaningful guidance, so the length is justified.

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 a single parameter and no output schema, the description covers what the return contains, how to identify the item, the expected call flow, and expiration handling. It could be slightly more explicit about the exact shape of the parsed result, but the examples and reference to the web UI modal provide adequate context.

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 already describes item_id, and schema coverage is 100%, so the baseline is 3. The description adds value by telling the agent where to get item_id (from get_bulk_job_items) and that it is the same ID the Data Service calls a query ID, which helps disambiguate the parameter 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 opens with a specific verb and resource: 'Fetch the parsed result data of a single bulk job item' and clarifies it returns the actual Amazon data produced by the item. It also distinguishes this from status-only tools by contrasting 'the DATA behind a specific item, not just its status' and by locating it within a typical flow after get_bulk_job_items.

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?

Usage guidance is explicit: use it after get_bulk_job_items when the user wants the data behind an item, and the typical flow list_bulk_jobs → get_bulk_job_items → get_bulk_item_result is provided. It also gives an alternative path for expired data by suggesting the matching real-time tool, which clarifies when to switch tools.

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