astrology_calculate_natal_chart

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

Annotations already indicate idempotent and read-only behavior. The description adds no contradictory information but also does not elaborate on aspects like input validation, potential errors, or calculation caveats. It is adequate but minimal.

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 front-loads the main action and uses a bulleted list for return values. It is informative but slightly verbose; could be trimmed without losing content.

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?

Given the complexity of natal chart calculation and no output schema, the description provides a solid overview of what is returned. It covers planetary positions, houses, angles, and aspects, but could specify aspect types or degree precision.

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?

Despite 0% schema description coverage at the top level, the description adds meaning for the main parameters (datetime, location, house system). It clarifies location can be coordinates or city string, and house system is configurable. This compensates for missing schema 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?

The description clearly states the tool calculates a natal chart based on date, time, and location, and lists specific outputs (planetary positions, houses, angles, aspects). It distinguishes from the sibling tool astrology_get_coordinates, which is for coordinate lookup.

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?

The description does not provide explicit guidance on when to use this tool versus alternatives. It mentions support for multiple house systems but lacks context about when not to use or prerequisites.

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