Uposatha days

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

Annotations already declare readOnly, idempotent and closed-world, so the description needn't restate safety. It adds genuine behavioral context beyond them: results are computed offline from a stated rule, labelled as computed rather than official, and local monasteries may observe a different day — an important accuracy caveat for the caller.

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?

Three front-loaded sentences: what it returns, the scoping parameters, then the provenance caveat. Efficient with no filler, though the tradition list partially duplicates the enum.

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?

With no output schema, the description usefully states that each day carries its lunar month and lunar day, and it discloses the computed-vs-official caveat. Limits like the 731-day span are left to the schema, which is reasonable.

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 100% and the enum already explains each tradition (Thai civil lunar calendar, Pakkhagaṇanā, Burmese calendar, poya days). The description's restatement of the four traditions adds no syntax or meaning beyond the schema, so the baseline of 3 applies.

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 names a specific resource (uposatha observance days) and a precise scope: full moon, new moon and the two half-moon days between two dates for one named tradition. An agent can tell this apart from general text-search siblings, though it never explicitly contrasts itself with the nearby 'festivals' tool.

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?

Usage is implied — compute observance days for a date range and a single tradition — but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as 'festivals' for culturally observed holidays.

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