Set Fill Light Distance

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

With no annotations, the description carries the burden of transparency. It explicitly states that the tool preserves azimuth and elevation angles, which is a key behavioral trait. However, it does not mention effects on other fill light properties (color, intensity) or any side effects.

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?

Two sentences, each providing essential information: the primary action and the preservation of angles. No unnecessary words or redundancy.

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 single parameter and no output schema, the description sufficiently covers the tool's purpose and key behavior. It does not explain return values (likely a void confirmation), but that is acceptable given the simplicity.

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 input schema has 100% coverage with a clear description for the 'distance' parameter. The description adds no extra detail about the parameter beyond what the schema already provides, so it aligns with the baseline for high coverage.

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 (set) and resource (fill light distance), and adds a unique behavioral detail (preserves current azimuth and elevation angles). This distinguishes it from sibling tools like set_fill_light_position_spherical which sets all spherical coordinates.

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 implies when to use this tool (when only distance needs adjustment), but does not explicitly state when not to use it or name alternative tools for other adjustments. Lacks explicit usage guidance beyond the implication.

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