calculate_menstrual_cycle

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

No annotations are provided, so the description carries full responsibility. It states only what the tool calculates and returns, without disclosing behavioral traits like read-only nature, error handling, or assumptions (e.g., regular cycles). This is insufficient for full transparency.

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 brief (two sentences) and directly states the purpose and outputs. It is efficient with no redundancy, but could be more front-loaded by placing the output list first.

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 having an output schema, the description lacks details on edge cases, error conditions, or how parameters affect results (e.g., cycle length). Given the medical nature and many sibling tools, more context is needed for reliable agent usage.

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 input schema covers 100% of parameters with descriptions and defaults, so the description adds limited value beyond listing output fields. The baseline of 3 is appropriate given the schema's adequacy, but the description could enhance understanding with usage examples 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?

The description clearly specifies the tool calculates next period, fertile window, and ovulation date, and lists the return fields. However, it does not explicitly differentiate from closely related sibling tools like calculate_ovulation, which may cause ambiguity.

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 only mentions 'See list_bundles for related 'sante' calculators' which provides minimal guidance. There is no explicit statement of when to use this tool versus alternatives, nor any indication of prerequisites or exclusions.

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