calculate_exposure_triangle

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

The description mentions return values but contradicts the required schema: it says 'given the other two' yet all parameters are mandatory. No annotations exist, so the description fails to clarify expected behavior or constraints.

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, no filler, front-loaded with the core action and result format. 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?

Despite mentioning return fields, the description omits crucial information about how to use the tool given the schema's insistence on all three inputs. It also does not reference the output schema structure.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds no additional parameter-specific semantics beyond restating the tool's purpose.

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 tool calculates a missing exposure parameter given the other two, which is specific and distinct from many other calculation tools. However, it does not explicitly differentiate from sibling photography calculators like 'calculate_depth_of_field'.

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 that two parameters are needed, but the input schema requires all three, causing confusion. There is no guidance on how to indicate which parameter to compute or alternatives.

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