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

Annotations already mark the tool as read-only and non-destructive, and the description adds valuable behavior beyond that: a 24-hour retention window, expiration behavior with a clear fallback message, and zero per-call credits. It also ties the output to the web app's item result modal, which is useful context. There is no contradiction with annotations.

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 core action, then adds usage flow, expiration caveat, and cost information in a logical order. Every sentence carries distinct information with no filler or redundancy.

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 tool with a fully documented schema, the description covers the output shape (depends on operation), usage sequence, lifecycle/expiration behavior, error fallback, and cost. Nothing essential is missing for an agent to select and invoke it correctly.

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 input schema has 100% coverage for the single item_id parameter, including where to obtain it and its query-ID alias. The description reinforces the idea of a specific item but adds no new parameter-level semantics beyond the schema, so it stays at the baseline.

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?

Opens with a specific verb and resource: 'Fetch the parsed result data of a single bulk job item' and clarifies that the returned data depends on the job's operation. It explicitly distinguishes from get_bulk_job_items by contrasting status with the data behind the item. This leaves no ambiguity about what the tool produces.

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?

Explicitly states the sequencing: use after get_bulk_job_items, and only when the user wants the actual data rather than status. It provides a typical flow (list_bulk_jobs → get_bulk_job_items → get_bulk_item_result) and names real-time fallback tools for expired results. This is strong when/alternative guidance.

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