Natal Chart Interpretation

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

Annotations include readOnlyHint=true, destructiveHint=false, which are consistent with the description. The description adds that it is 'Token-cached for repeats' but does not elaborate on caching behavior. Given the annotations, the description adds minimal extra context about the tool's 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?

The description is concise: one sentence for purpose, then key features (multi-language, token-cached), cost, and an example. No unnecessary information. The purpose is front-loaded.

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?

The tool lacks an output schema, and the description does not explain the output format (e.g., structured vs free text). It mentions contents like personality traits and archetypes but not how they are presented. For an AI generation tool, this is a notable gap.

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?

The input schema coverage is 100%, and the schema already describes parameters. The description adds context beyond the schema by noting defaults for lat/lon/tz and emphasizing accuracy, plus an example request. This adds meaningful guidance for parameter usage.

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 'Generate AI interpretation of a natal chart — personality traits, life themes, strongest archetypes', which is specific and distinguishes it from sibling tools like interpret_synastry and interpret_transits. The title 'Natal Chart Interpretation' reinforces the purpose.

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 hints at usage with 'Multi-language' and 'Token-cached for repeats', and mentions cost and an example request body, but does not explicitly state when to use this tool versus alternatives like interpret_placement or report_ai_natal_narrative. No exclusions or alternatives are provided.

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