natal_moon

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

With no annotations provided, the description carries full burden and does well: it discloses default time (12:00), default timezone (UTC), warns that sign may be inexact if Moon changes signs, and emphasizes timezone must be the birth location's then-effective zone. This goes beyond basic operation.

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?

Every sentence serves a purpose: main action, usage trigger, fallback behavior, and parameter specifications. The Args section is cleanly structured without redundancy.

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?

Output schema exists, so return values need not be explained. Input handling, defaults, and edge cases (unknown time, wrong timezone) are all covered. This is complete for a computational astrology tool.

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 coverage is 0%, but the description explains each parameter in detail: date format (ISO 8601), time format (24-hour HH:MM) plus default, tz format (IANA) plus default and correctness caveat. Fully compensates for the schema's lack of descriptions.

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?

Description uses a specific verb+resource: 'Compute the natal (birth) Moon placement' and lists concrete outputs (zodiac sign, phase, illumination). It clearly distinguishes from siblings like 'moon_current' by tying to birth date/time context.

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 usage trigger is given: 'Use this when the user asks "what was my moon sign?" or gives a specific birth date/time...'. It also provides guidance for missing time and timezone caveats, though it doesn't explicitly name alternative tools for when not to use.

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