get_render_settings

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

No annotations are provided, so the description carries the behavioral disclosure burden. The verb 'Get' clearly indicates a read-only action, which is useful, but the description does not disclose return format, error behavior, or whether the node must be cooked. It covers the core operation but not deeper behavioral traits.

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 appropriately sized for a one-parameter getter: a single purpose sentence followed by a minimal args list. Every word adds value, and the main purpose is front-loaded.

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?

The tool is simple: one parameter, no output schema, no annotations. The description gives the essential information needed to call it correctly—what it does and what parameter it requires. It is complete enough for a straightforward getter, though it could mention what a typical return looks like.

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%, so the description must compensate for the single parameter. 'node_path: ROP node path' adds the fact that the path refers specifically to a ROP node, which is more specific than the schema's generic 'Node Path' title. However, it does not provide path format, examples, or additional constraints.

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 states a specific verb ('Get render settings from a ROP node') with a clear resource and scope. It clearly differentiates itself from the sibling set_render_settings by being the getter counterpart, and the ROP-node context is explicit enough to avoid confusion with other get_* tools.

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 usage context is implied: this tool retrieves render settings from a ROP node, which contrasts with setters like set_render_settings. However, there is no explicit guidance on when to use this versus alternatives like setup_render or render_node_network, and no exclusions or prerequisites are stated.

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