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

The description fully discloses the output ('obturador recomendado y una tabla') and the rule used. Annotations declare readOnlyHint=true, and the description aligns, indicating no destructive effects. No contradictions.

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 that efficiently state purpose, the rule, and the output. No redundant or extraneous information. Ideal length for quick comprehension.

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?

The tool is simple with one parameter and no output schema. The description adequately covers what it does, the rule, and what it returns. No gaps given the low complexity.

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 single parameter (fps) has high schema coverage (100%), and the description adds value by explaining the 180-degree rule rationale ('el obturador debe ser el doble del frame rate'), enriching understanding beyond the schema's basic description.

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 the correct shutter speed for video based on the 180-degree rule, which directly differentiates it from sibling tools like calcular_camara_lenta (slow motion calculations) and calcular_filtro_nd_video (ND filter calculations). The verb 'calcula' and specific resource 'velocidad de obturación' make the purpose unambiguous.

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 explains the tool's function but does not explicitly state when to use it versus alternatives (e.g., when to use this instead of calcular_camara_lenta). The context is clear but lacks exclusionary guidance, so it scores at the 'implied usage' level.

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