start_render

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

The description explicitly warns that the tool is 'known to crash the MCP connection (WinError 10054)' and instructs to pass allow_dangerous=True to proceed. This is a critical behavioral disclosure well beyond what schema or annotations (none) provide, making the tool's risk profile transparent.

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 two concise sentences: a clear purpose followed by a critical warning. It is front-loaded with the action and resource, with no unnecessary words or repetition.

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?

Given the lack of annotations, output schema, and parameter descriptions, this description is incomplete. It lacks details about what 'path' should be, what 'frame_range' does, the expected behavior after starting a render, and any return values or side effects beyond the crash warning.

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?

Only the allow_dangerous parameter is explained ('Pass allow_dangerous=True to proceed'). The required 'path' parameter and optional 'frame_range' are not described at all, and with 0% schema description coverage, the description fails to compensate for the missing semantic meaning.

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 action ('Start a render') and the resource ('from a ROP node'), which is specific and understandable. However, it does not explicitly differentiate among the many render-related sibling tools (e.g., render_flipbook, render_single_view), so it is clear but not fully distinguishing.

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 on when to use this tool versus alternatives. The only usage hint is the warning that allow_dangerous=True is required to proceed, which is a conditional instruction, but it does not help select this tool over other render options.

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