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

With no annotations supplied, the description does real work: it discloses the return shape, that the download is a plain HTTP GET requiring no auth header, that the URL expires in 24 hours, and that re-invoking yields a fresh one. The notable gap is failure behavior when the job is not yet complete.

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 sentence, front-loaded with the outcome and followed by the operational caveats that matter. No filler or redundant restatement of the tool name.

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?

Because there is no output schema, the description correctly carries the burden of explaining return values (assetId, downloadUrl) and the expiry/refresh cycle. Only the incomplete-job error path and jobId sourcing are left unstated for a one-parameter 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?

Schema coverage is 0% and the single required jobId has no description in the schema. The description implicitly ties it to a render job but gives no format, provenance, or example, so it adds only marginal meaning beyond the property name.

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 names a specific verb and resource ('Get a completed render job's result') and enumerates the returned fields (assetId, downloadUrl). It implicitly separates itself from render.status/render.list_for_project by scoping to *completed* jobs, though it never names those siblings.

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 phrase 'completed render job's result' implies the precondition that the job must be finished, and the parenthetical tells the agent to call again for a fresh URL. However, it never explicitly states what to do first (poll render.status) or what happens if the job is still running, leaving the when-not condition to inference.

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