get_natal_chart

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

No annotations provided, so description carries full burden. It discloses default systems (tropical, Placidus) and fallback behavior for certain house systems. However, it does not mention read-only nature, auth, or output format. For a computation tool, it is fairly transparent.

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?

Single sentence covering essential elements, but could be more structured or broken into bullet points. Still efficient with no wasted words.

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?

No output schema, but description lists included chart components (positions, houses, aspects, ASC/MC, lunar phase, Hermetic Lots). Adequate for an astrological tool with 7 parameters. Could mention return format or error cases, but not required.

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 100%, so baseline is 3. Description adds minimal new info beyond schema: it mentions local date/time and IANA timezone, already in schema descriptions. No additional parameter semantics.

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 clearly states it computes a full natal chart with houses, aspects, ASC/MC, lunar phase, and Hermetic Lots, distinguishing it from sibling tools like get_planet_positions or get_aspects. Specific verb 'get' and resource 'natal chart' make purpose unambiguous.

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?

Implicitly indicates use for comprehensive chart vs alternatives, but lacks explicit when/when-not instructions. Still, the description of what it includes (houses, aspects, etc.) clarifies its scope relative to siblings.

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