render_status

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

With no annotations, the description carries the behavioral disclosure burden. 'Return' clearly signals a read-only operation, and the listed output categories are helpful. However, it does not disclose whether the job must be active, whether it can be polled repeatedly, or what happens for completed/failed renders.

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?

A single front-loaded sentence with zero filler. Every word adds useful information, and the structure is easy to scan.

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?

For a simple read-only status tool the description lists the key return categories, but without an output schema, annotations, or sibling guidance it remains incomplete. An agent still lacks context about valid job_id states, polling semantics, and failure behavior.

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 description coverage is 0%, and the description does not mention job_id at all. The parameter's purpose is inferable from its name, but the description adds no meaning about how the id is obtained, its format, or how it maps to a render job.

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 resource ('current phase, elapsed time, diagnostics, and output paths'), making it clear this is a render status query. The listed fields distinguish it from siblings like render_result, interactive_viewer_status, and render_preview without needing to inspect schemas.

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?

No guidance is given on when to call this tool versus alternatives such as interactive_viewer_status, render_result, or cancel_render. There are no stated prerequisites, exclusions, or sibling differentiators beyond the implied status-polling use case.

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