Calculates the Yahrzeit, the anniversary of the day of death of a loved one, according to the Hebrew calendar for a specified date
| Name | Required | Description | Default |
|---|---|---|---|
| date | Yes | Gregorian date of death (in yyyy-MM-dd format) | |
| afterSunset | Yes | after sunset |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral burden, and it only states that the tool calculates. It does not explain how 'afterSunset' affects the result, what the returned value looks like, or how edge cases are handled.
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?
A single front-loaded sentence defines the term and states the calculation target with no filler. It is appropriately sized for a tool whose schema handles parameter details.
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 requires two parameters, one of which has a confusing description, has no annotations, and has no output schema. A complete definition would explain the afterSunset semantics and at least hint at the return value (Hebrew date vs. Gregorian date).
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 schema already documents 'date' clearly and provides 100% parameter coverage, so the baseline is 3. The description adds no additional meaning; notably, it does not clarify the ambiguous 'after sunset' boolean, which is a required input.
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 states a specific verb and resource: it calculates the Yahrzeit from a Gregorian date of death, which clearly distinguishes it from the conversion and schedule tools in the sibling list. However, it never names a sibling or explicitly contrasts itself, so it stays at 'clear but no explicit differentiation'.
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 definition implies the tool is for computing the Hebrew-calendar anniversary of a death date, and the siblings make it easy to infer this is not for general date conversion or holiday lookup. It provides no explicit 'use when' guidance, no exclusions, and no mention of alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: two cover bidirectional date conversion, while the others handle unique calendar computations like holidays, Torah portions, Shabbat times, Daf Yomi, and Yahrzeit. There is no overlap or ambiguity between them.
All tool names use lowercase hyphenated words, creating a uniform style. However, some names are verb-led (convert-gregorian-to-hebrew) while others are noun-led (daf-yomi, shabbat-times), which is a minor deviation from a single naming pattern but remains readable and predictable.
With 7 tools, the server is well-scoped for a Jewish calendar domain. Each tool addresses a distinct functionality, and the count fits comfortably within the ideal range for a focused utility server.
The server covers the core Jewish calendar needs: date conversion, annual holidays, Shabbat times, Torah portions, Daf Yomi, and Yahrzeit. A minor gap is the lack of a tool for a specific holiday date lookup (without retrieving the whole year) or more advanced halachic time calculations, but these are workable gaps.
