set_render_settings

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 only says 'Set render settings,' which implies mutation but does not mention side effects (e.g., triggering a recook), whether existing settings are overwritten, required permissions, or what happens on invalid settings. This is almost no behavioral transparency beyond the basic action.

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, concise sentence with no fluff. However, it is under-specified for a tool with an opaque settings object and no annotations. Conciseness is good, but it sacrifices necessary detail, so a middle score is appropriate.

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 complexity of an object-typed 'settings' parameter, no annotations, no output schema, and no return-value documentation, the description is far too minimal. It lacks information about the settings structure, error behavior, and expected side effects, leaving an agent to guess at critical execution details.

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% for the 2 parameters. The description mentions 'render settings' and 'ROP node' but does not explain the structure of the settings object, what valid keys exist, or the expected path format. It adds essentially no semantic meaning beyond the parameter names in the schema.

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+resource: 'Set render settings on a ROP node.' It clearly distinguishes from sibling tools like get_render_settings (get vs set) and create_render_node (existing node vs create). However, it does not explicitly call out these alternatives, so it stops short of 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?

No guidance is provided on when to use this tool vs alternatives such as set_parameter or get_render_settings. There is no mention of prerequisites (e.g., the ROP node must already exist) or context for typical usage. This is effectively no usage guidance, meriting a score of 2.

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