Get Fill Light Size

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

No annotations are provided, so the description must disclose behavior. It indicates a read-only operation ('Get') and hints at non-destructive use by suggesting it can be cached. However, it does not explicitly state that it has no side effects or require authentication, but as a simple getter, this is mostly sufficient.

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 two sentences long: first sentence states the purpose, second sentence provides usage guidance. No wasted words, well-structured, and front-loaded with key information.

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 no output schema, the description mentions returning 'width and height in units' but does not specify the exact structure or data types. For a simple getter, this is mostly complete, but a bit more detail on the return format could improve it. Most importantly, it covers the essential info for correct use.

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?

With zero parameters and 100% schema description coverage, the description does not need to add parameter info. Baseline for 0 params is 4. The description focuses on output instead, which is appropriate.

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 'Get the current fill light area size (width and height in units)', providing a specific verb ('get') and resource ('fill light area size'). It distinguishes from sibling tools like get_fill_light_color or get_fill_light_position_spherical by focusing on size.

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 explicitly advises to 'Query this before relative size changes to ensure accuracy' and notes that for absolute changes, 'you may use recently queried state from context if no manual interactions occurred'. This provides clear when-to-use and when-not-to-use guidance, differentiating it from direct set operations.

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