render_result

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

With no annotations, the description carries the full burden of disclosing side effects and edge-case behavior. It only states the return contents; it does not say what happens for a missing, incomplete, or failed job, whether it blocks, or whether it is safe/idempotent.

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, no filler, and the core verb and object are front-loaded. It is concise, though 'job report' is somewhat underspecified; a concrete definition of the report format or completion condition would make it fully effective.

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?

The output schema covers return values, so the brief output listing is acceptable. However, for an agent choosing among many render-related siblings, the absence of a completion prerequisite or alternative routing leaves a meaningful gap in selecting and invoking 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 description never mentions job_id or explains that the single parameter identifies the job whose report is returned. With 0% schema description coverage, the description should compensate, but it only relates to the parameter indirectly through the tool's purpose; the schema's title 'Job Id' remains the main semantic cue.

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 ('Return') and names the resources ('completed job report', 'PNG preview'), making the core purpose understandable. It does not explicitly contrast with siblings like render_status or render_preview, but the completed/report wording distinguishes it from status or intermediate preview 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?

There is no guidance about when to call this tool instead of render_status, render_preview, or capture_render_snapshot. The words 'completed' and 'when available' imply it should be called after job completion, but no explicit condition, prerequisite, or excluded alternative is stated.

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