list_render_nodes

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

No annotations are provided, so the description carries the full disclosure burden. It does state scope implicitly (all render nodes, entire scene, unfiltered), which is useful, but it says nothing about traversal depth, return format, ordering, or whether it includes nested/subnet ROPs.

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 sentence with no wasted words, front-loaded with the action and resource and using the parenthetical only to disambiguate terminology.

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 no-parameter, no-output-schema read tool this is nearly sufficient; the agent knows what it lists and where. The only missing piece is scope detail (recursive vs top-level network, returned fields), which is minor given the tool's simplicity.

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 per the rubric this is a baseline 4. There are no parameters for the description to explain, and nothing misleading is stated about inputs.

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 gives a specific verb (list) and resource (render/ROP/Driver nodes) and clarifies the Houdini terminology with a parenthetical, so the agent immediately knows what comes back. It does not, however, explicitly distinguish this from nearby siblings such as render_node_network or create_render_node, which would be needed for a 5.

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?

Usage is only implied: an agent can infer this is the read-only lookup for ROP nodes, but there is no statement of when to use it versus alternatives (e.g., get_render_settings, render_node_network) and no conditions or exclusions given.

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