sabbats

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

With no annotations, the description carries the behavioral burden. It discloses that southern hemisphere dates are offset by ~6 months and that hemisphere defaults to 'north', which are key behavioral traits. It doesn't explicitly mention read-only status but that is implied for a listing tool.

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 tightly written: purpose first, then usage examples, then behavioral note, then parameter definitions. Every sentence adds value, no redundancy or fluff.

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?

Comprehensive for a simple two-param listing tool. Covers purpose, usage, hemisphere behavior, parameters, and output schema is present. No significant gaps.

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 has no descriptions (0% coverage), but the description fully explains both parameters: year (optional, current year if omitted) and hemisphere (north/south, with default and reason for offset). This goes well beyond the schema.

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 lists Wheel of the Year sabbats with specific dates for a given year and hemisphere. It provides the exact sabbat names and examples of user queries, distinguishing it from sibling tools like moon_phases or solar_terms.

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?

Explicit when-to-use guidance is given via example queries and reference to the pagan/wiccan wheel of the year. However, no alternatives or when-not-to-use exclusions are stated, though sibling names make the scope fairly clear.

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