Natal

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

No annotations are provided, so the description carries the full burden. It usefully discloses that the supplied hour is local to the coordinates and that the timezone is resolved automatically, which is important operational context. However, it does not state that this is a read-only calculation, nor does it mention auth or rate-limit behavior.

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?

Two sentences with no filler, front-loading the outputs followed by the time-handling caveat. Every sentence earns its place and the information is easy to parse.

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?

An output schema exists, so return values need not be explained. But with no annotations and 0% parameter schema coverage, the description is incomplete about input parameters and when to use the tool; it only covers purpose and timezone behavior.

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 0%, so all seven parameters lack descriptions. The description clarifies that hour is local time and that timezone is auto-resolved, which adds context for the date/time parameters, but it does not explain lat/lon units or ranges, nor the date/time format. It partially compensates but falls short for a seven-parameter 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?

States a specific resource set: planetary positions, house cusps, and aspects for a birth moment. However, it does not explicitly distinguish itself from sibling astrology tools such as transit_today or daily_horoscope; the 'natal' name and 'momento de nacimiento' phrase imply a birth chart but no sibling routing is provided.

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?

No when-to-use guidance, prerequisites, or alternative tools are mentioned. The description explains time handling but gives no criteria for choosing this tool over siblings like transit_today or moon_phase.

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