Set Key Light Position (Spherical Coordinates)

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

No annotations, but description clearly states it only changes azimuth/elevation and preserves distance, and explains coordinate conventions. Lacks mention of side effects or permissions, but adequate for typical usage.

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 concise sentences with essential info front-loaded. No wasted words.

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?

Covers all needed aspects for a 2-param tool with no output schema: effect, coordinate system, direction names. Lacks mention of prerequisites or undo, but still informative.

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 covers both parameters with detailed descriptions. Tool description adds examples and direction names list but is largely redundant with schema (100% coverage). Does not significantly extend understanding beyond 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?

Clearly states verb 'Set', resource 'key light position', and coordinate system 'spherical coordinates'. Explicitly says it preserves distance, differentiating from distance-setting siblings.

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?

Implicitly indicates use for angular adjustments only. No explicit when-not-to-use or alternative tool references, but context from sibling names makes it clear.

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