list_render_nodes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly signals a read-only listing operation, but it does not reveal what the returned data looks like, whether both ROP and Driver nodes are returned as the same type, or whether the list covers nested/network-level nodes.

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 efficient sentence that front-loads the verb, resource type, and scope. The parenthetical 'ROP/Driver' adds useful domain clarification without bloating the text.

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 parameterless, read-only list tool, the description is largely complete: it names the resource, the scene scope, and the action. The main gap is the lack of any statement about the return format, but no output schema exists and the operation is simple enough that this is a minor omission.

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 tool takes zero parameters, so there is no parameter meaning to compensate for. The schema already exhaustively documents an empty parameter set, and the description need not add anything.

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 ('List') plus a well-defined resource ('render (ROP/Driver) nodes') and scope ('in the scene'). This distinguishes it clearly from siblings like create_render_node and get_render_settings, which either create render nodes or read settings rather than listing existing nodes.

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 description gives no guidance about when to choose this tool over alternatives, and does not mention exclusions or related tools. It simply states the action, leaving the agent to infer the appropriate context without support.

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