calculate_crop_factor

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

No annotations are present, so description must cover behavior. It states the calculation but does not disclose return format, side effects, or assumptions (e.g., full-frame reference). Minimal but not misleading.

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, front-loaded with core purpose, second sentence directs to related bundle. No superfluous 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?

Output schema exists but is not shown; description lacks clarity on how equivalent focal length is computed without focal length input. For a simple tool it covers basics, but missing explanation could confuse.

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 has 100% description coverage, so baseline 3. Description adds little beyond schema: 'based on sensor width' is redundant. No extra meaning about units or constraints.

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?

Description clearly states verb 'calculate' and specific resources 'camera crop factor and equivalent focal length' with input 'sensor width'. Effectively distinguishes from many sibling calculator tools.

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?

Description references list_bundles for related photography calculators but does not explicitly state when to use this tool versus alternatives. No exclusions or when-not scenarios are provided.

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