ovulation_calc

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

No annotations are provided, so the description carries the full burden. It only states the calculation purpose but does not disclose behavioral details such as the return format, assumptions (e.g., typical ovulation day 14), or any limitations. The output schema exists but the description should add context.

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 short and to the point, but it includes a parameter list that could be integrated more naturally. Still, every sentence adds value, and it is front-loaded with the purpose.

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 the tool has an output schema and only 2 simple parameters, the description provides adequate context for an AI agent to use the tool. However, it could mention that the calculation uses the typical 14-day luteal phase assumption to fully set expectations.

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 description coverage is 0%, so the description must compensate. It explains both parameters: last_period as 'First day of last menstrual period (ISO date)' and cycle_days as 'Average cycle length in days (default: 28).' This adds meaningful semantics beyond the schema's type and default.

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's purpose: 'Calculate ovulation window and fertile days.' The verb 'calculate' and resource 'ovulation window and fertile days' are specific and distinct from sibling tools like calculate_bmi or due_date_calc.

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 lists parameters and their meanings, implying the tool is used when one has last period date and cycle length. However, it does not explicitly state when to use versus alternatives (e.g., due_date_calc) or provide exclusions.

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