blender_scene_set_settings

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

Annotations already provide idempotentHint=true and destructiveHint=false. Description adds little beyond the bare purpose, not disclosing that settings are overwritten or that operation is safe. Does not contradict annotations.

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?

Description is short: one sentence plus bullet-like Args/Returns. No wasted words, but could be more structured with explicit parameter details.

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 tool has one complex parameter with multiple fields, schema descriptions are minimal, and annotations exist, the description is adequate but incomplete. It doesn't mention the scene_name parameter or idempotent nature.

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% according to context, and the description only says 'params: Scene settings parameters' without explaining each field's meaning, constraints, or defaults. Schema has minimal descriptions like 'Frame rate' but description doesn't compensate.

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 'Set scene settings' and lists examples like frame range, frame rate, unit system, which clearly indicates the verb and resource. It distinguishes from sibling scene tools (create, delete, get_info) but lacks clarity on whether it applies to active scene or specified scene via scene_name parameter.

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 on when to use this tool versus alternatives like blender_scene_create or blender_scene_get_info. No when-not-to-use or prerequisites mentioned.

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