Get a generation result

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

With no annotations provided, the description carries the full burden and delivers extensive behavioral detail: the server uses its own API key, saves the file locally and returns its path, inlines small media as base64, streams large/video media directly, handles arbitrarily large files, and never exposes the API key or raw URL. This goes far beyond basic expectations.

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 bit dense, containing four sentences, but every sentence provides essential behavioral or security information. It is front-loaded with the core purpose, and while it could be slightly more streamlined, it remains efficient and free of fluff.

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?

Despite being a relatively simple tool with two parameters and no output schema, the description fully covers return behavior (path vs. inline base64 vs. streaming), handling of large media, and security guarantees. It provides everything an agent needs to invoke and understand the outcome, leaving no significant gaps.

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 coverage is 100%, with both parameters clearly described in the schema. The description adds the context that the result media belongs to a COMPLETED generation, reinforcing publicId, but does not add meaning beyond the schema. Thus 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 opens with 'Fetch a COMPLETED generation's result media,' using a specific verb and resource, and clearly distinguishes from the sibling tool deepy_get_generation by focusing on the actual result media rather than the generation status or metadata.

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 emphasizes that the generation must be COMPLETED, providing clear context for when the tool is appropriate. It does not explicitly name alternative tools or state when not to use it, but the prerequisite and scope are clear enough for an agent to choose correctly.

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