Toplu İşlem Sonucu (getBatchRequestResult)

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

With no annotations provided, the description carries the full burden. It discloses that results are queryable for up to 4 hours and that stock-price updates do not return batch status. This is valuable behavioral context beyond the minimal read-only assumption. No contradictions exist.

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 concise (two sentences plus a note) and includes critical exceptions. It is front-loaded with the purpose. While efficient, there is minor room for improvement in separating general usage from special cases.

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?

Given the low complexity (1 parameter, no output schema), the description covers the necessary context: what it does, when to use, key response fields, time limit, and a special case. It provides complete guidance for an agent to select and invoke the tool 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 single parameter (batchRequestId) is fully described in the schema (100% coverage). The description adds context about the source of the ID but does not provide additional semantic detail beyond what the schema states. Baseline 3 is appropriate.

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 tool's purpose: querying the result of batch operations (createProducts, updateProducts, etc.) using a batchRequestId. It specifies the operations and response fields (status, failureReasons), and even notes an exception for stock-price updates, effectively distinguishing it from sibling tools.

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 explains when to use the tool (after batch operations) and provides guidance on interpreting results, including the exception for stock-price updates. However, it does not explicitly state when not to use it or mention alternative tools, though the context of sibling tools makes alternatives clear.

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