ledfx_refresh_blender_scenes

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

No annotations are provided, so the description must carry the full burden. It discloses that the tool recreates scenes without activation, but it does not mention potential side effects (e.g., overwriting existing scenes, impact on active scenes) or prerequisites. More detail is needed for safe and informed use.

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 that conveys the essential action and a critical constraint without any wasted words. It is front-loaded and efficient.

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 tool with no parameters and no output schema, the description provides the basic purpose and a key constraint. However, it lacks details on what exactly 'recreate' entails (e.g., overwriting behavior, persistence) and does not describe the return value. It is adequate but not fully comprehensive.

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 has no parameters, so schema coverage is 100%. The description does not need to add parameter information. Baseline for zero parameters is 4, and the description meets it adequately.

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 clearly states the action ('recreate all blender scenes') and the resource ('using their stored virtual configurations'), with a key differentiator ('no scene activation') that distinguishes it from siblings like ledfx_activate_scene.

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 description implicitly indicates when to use this tool—to refresh scenes without activation—by explicitly noting 'no scene activation'. However, it does not explicitly state when not to use it or mention alternative tools, but the context of siblings makes it reasonably clear.

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