ilovevideoeditor_get_render_status

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

No annotations are provided, so the description must disclose behavioral traits itself. It only restates the tool's purpose ('Check the status') without adding information about whether it is read-only, whether it can be polled, how it handles errors, or what the response format is. This is a minimal disclosure that does not go beyond the tool name's implication.

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 single sentence that is direct and front-loaded with the main action and resource. It contains no filler or redundant information, effectively communicating the tool's purpose in a concise manner.

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 no output schema and no annotations, the description should provide more context about the tool's behavior and result interpretation. It does not mention possible statuses, polling behavior, or what the response looks like. While the tool is simple, the missing context makes it incomplete for an agent to know what to expect.

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 covers 100% of the parameters, and the schema's description of jobId ('returned by ilovevideoeditor_render_json or ilovevideoeditor_render_template') is more informative than the tool description's simple 'by its job ID.' The tool description adds no additional meaning to the parameter beyond what the schema already provides, so a baseline score 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 clearly states the tool's function: 'Check the status of a render job by its job ID.' It specifies the action (check), the resource (render status), and the required input (job ID). This distinguishes it from sibling tools like render_json/render_template (which start jobs) and get_download_url (which retrieves the final result).

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 tool description itself does not explicitly mention when to use it or alternatives. However, the context is implied: one must first create a render job via render_json or render_template, and then poll its status. No exclusions or alternative tools are referenced in the description, making the usage guidance merely implied rather than explicit.

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