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

With no annotations, the description carries the behavioral burden. It clearly indicates a read-only fetch operation and discloses the meaningful behaviors: status values returned and that output_url is only present when completed. It does not discuss not-found/error behavior, but for a simple read operation this is adequately transparent.

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?

One dense, well-structured sentence that front-loads the action and resource, then adds the conditional return detail. No filler or redundant restatement.

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?

With only one parameter and full schema coverage, the description provides enough context for a typical read operation. It explains the statuses and the conditional output_url, though it does not mention error cases or 404 behavior, which are minor for this low-complexity tool.

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 fully documents the single 'id' parameter at 100% coverage. The description adds that the id refers to a transcode job, but does not need to add much beyond the schema, so the baseline of 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 uses a specific verb ('Fetch'), a clear resource ('current state of a single transcode job'), and identifies it by ID. It also enumerates the key return content (status values and output_url), which fully distinguishes it from siblings like list_transcodes and transcode_video.

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 implies the use case: when you need the current state of one transcode job given its ID. However, it does not explicitly state when to prefer this over list_transcodes or the polling/wait variants, nor does it name alternatives.

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