render_set_quality

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

Beyond the destructiveHint annotation, the description discloses a key behavioral trait: 'anything it does not understand is silently ignored.' It also directs the agent to render_get_settings for verification, which is especially valuable because there is no output schema describing return values. This tells the agent not to assume the operation fully succeeded.

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 logically ordered: action, caveat, verification. The bilingual duplication makes it longer than strictly necessary, but both language blocks are succinct and the key information 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?

For a mutation tool with no output schema, it covers the most important operational facts: what it sets, when settings are ignored, and how to confirm the result. It does not explicitly address calling with no parameters or name the active renderer, but those are minor gaps given the full schema coverage and the explicit verification pointer.

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 100%, so each parameter already has an explanatory description. The tool description adds examples like aaSamples and samples and explains the ignore-if-unsupported behavior, but it does not meaningfully change per-parameter semantics beyond what the schema already provides.

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 opens with a specific verb and resource: 'Set a generic quality/sampling knob', and clearly specifies it also writes renderer-specific sampling properties like aaSamples and samples. It is easily distinguished from sibling render tools such as render_set_resolution or render_set_engine.

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?

It gives clear context for when to use it: when a generic quality/sampling adjustment is needed. It also warns that unsupported properties are silently ignored and tells the agent to verify the result with render_get_settings. It does not explicitly name alternatives or list when not to use it, but the scope is sufficiently clear.

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