Western Astrology MCP Server by RoxyAPI

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

With no annotations, the description fully describes behavior: it generates forecasts from real-time planetary transits using whole-sign houses, returns multiple categories (love, career, health, etc.), includes Moon details and lucky elements. It does not explicitly state it is read-only or address rate limits, but for a data retrieval tool, this is sufficient.

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 four sentences with a fifth sentence that appears to be keyword stuffing ('Daily horoscope API, zodiac forecast, sun sign horoscope, astrology prediction'), which adds no value for an AI agent. The core information is clear, but the filler detracts from conciseness.

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 lack of an output schema, the description lists the return fields (love, career, health, finance, overview, etc.) and explains the generation method. This is sufficiently complete for a daily horoscope tool, covering what the agent needs to know about the response.

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% with descriptions for all 4 parameters. The description adds minimal extra value beyond the schema; it mentions the date parameter supports editorial scheduling, but the schema already states that. No additional insight for other parameters.

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 explicitly states 'Get the daily horoscope for any zodiac sign' using a specific verb and resource. It distinguishes itself from sibling tools like monthly and weekly variants by specifying 'daily' and mentioning 'transit-based forecast with house activations'.

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 clearly indicates it is for daily horoscope forecasts by zodiac sign. While it does not explicitly compare to monthly/weekly siblings, the name and title make the daily focus obvious, and the context of sibling tools provides implicit guidance.

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

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

No annotations provided, but the description details the coverage (love, career, health, finance), key dates from ephemeris, and the compact parameter for token optimization. It does not mention rate limits or data freshness.

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 clear but includes redundant keyword phrases like 'Monthly horoscope API, zodiac monthly forecast, astrology monthly prediction' which could be removed for conciseness.

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 the description adequately explains the response contents: week-by-week breakdown, key dates, and areas covered. Lacks details on response structure but sufficient for understanding.

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% with clear parameter descriptions. The tool description adds context about the output but does not significantly enhance parameter understanding beyond the 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?

The title and description clearly state the tool returns a monthly horoscope for a zodiac sign with week-by-week breakdown and key lunar dates. It distinguishes from sibling tools like daily and weekly horoscopes.

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 guidance on when to use this monthly tool versus the daily or weekly siblings, nor does it mention any prerequisites or alternatives.

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

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

No annotations provided, so the description carries full burden. It discloses that forecasts are based on planetary transits and house-based content, and lists covered areas (love, career, etc.). It does not disclose authentication needs, rate limits, or response shape, but is adequate for a straightforward API.

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 first two sentences are efficient, but the third sentence ('Weekly horoscope API, zodiac weekly forecast...') is redundant keyword stuffing that adds no value. Overall reasonably concise but has unnecessary repetition.

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 exists, so the description partially compensates by listing output content (love, career, health, finance, lucky days). However, it does not describe the JSON structure or whether results are text vs. structured data. Adequate for a simple horoscope 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 covers all 3 parameters with descriptions (100% coverage, baseline 3). The description adds no additional meaning beyond what the schema provides; it does not explain lang, sign, or compact further.

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 it returns a weekly horoscope for any zodiac sign, using specific verbs ('Get weekly horoscope') and resources ('zodiac sign'). It distinguishes from daily/monthly siblings by specifying '7-day period', though it does not explicitly contrast with them.

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?

Usage is implied by timing ('weekly'), but no explicit guidance on when to use this versus alternative horoscope tools (daily, monthly) or exclusions. The description does not mention prerequisites or alternatives.

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

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

No annotations are provided, so the description carries full burden. It only describes what the tool does, not any behavioral traits like authentication requirements, rate limits, or data limitations. This is insufficient for a tool with no annotations.

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 short sentences, front-loaded with the core purpose followed by use cases. No extraneous 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?

The description mentions the key output ('moon phase and illumination') and the tool's purpose. Given no output schema, it could specify more about the data structure, but it is adequate for a simple list 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 100%, and the schema descriptions are already informative. The description does not add meaning beyond what the schema provides, so baseline 3 applies.

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 uses a specific verb ('Get') and resource ('lunar calendar') and clearly scopes it to a month. It distinguishes itself from siblings like get_astrology_moon_phase_current and get_astrology_moon_phase_upcoming by focusing on the entire month's data.

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 states it is 'Perfect for creating moon phase calendars, lunar planners, and astrology event schedules,' providing context for when to use it. It does not explicitly exclude alternatives, but the sibling set allows inference.

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

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

Without annotations, the description carries the full burden. It discloses that time affects precision ('Moon moves ~13 degrees per day') and lists all return fields. No contradictions found.

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 two sentences, front-loaded with key output details, and contains no fluff. Every sentence adds value.

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?

While there is no output schema, the description explains the return value comprehensively (phase name, illumination, etc.). It does not cover error cases, but for a simple data retrieval tool, it is largely complete.

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% and all parameters are described in the schema. The description adds minimal additional semantic context beyond what the schema provides, meeting baseline expectations.

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 returns 'current moon phase with illumination percentage, lunar age, zodiac sign, and distance from Earth.' It specifies the exact phase names and purpose for moon tracking, lunar calendars, etc., making it distinct from sibling tools like get_astrology_moon_phase_calendar_year_month.

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 mentions use cases like 'moon tracking apps, lunar calendars, astrology widgets' but does not explicitly contrast with siblings such as get_astrology_moon_phase_upcoming or the calendar tool. However, the name and context imply it is for a single date/time, providing implicit guidance.

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

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

With no annotations, the description must convey behavioral traits. It states it returns dates and phase names for lunar quarters, but does not address timezone handling, behavior when startDate is in the past, or whether the count includes phases starting from startDate. Basic but missing edge-case details.

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 extremely concise with three sentences, each adding value: what it does, what it returns, and use cases. No wasted words or 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?

For a tool with 4 parameters, 1 enum, and no output schema, the description explains the return type (dates and phase names) but lacks explicit output structure (e.g., array of objects). Adequate for simple usage but could be more detailed.

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%, and the input schema already provides detailed descriptions for all four parameters (lang, count, compact, startDate). The tool description adds no additional parameter information beyond the schema, so baseline 3 applies.

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 it retrieves upcoming moon phase transitions (New Moon, First Quarter, Full Moon, Last Quarter) for upcoming weeks/months, distinguishing it from sibling tools like get_astrology_moon_phase_current (single current phase) and get_astrology_moon_phase_calendar_year_month (specific month/year).

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 provides context with 'Perfect for lunar event calendars, moon phase widgets, and astrology planning tools,' implying appropriate use cases. However, it does not explicitly mention when not to use it or compare to siblings like get_astrology_moon_phase_current.

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

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

With no annotations, the description carries full burden. It clearly states what the tool returns (list of planets with core info) and contrasts with the detailed version. While it doesn't mention rate limits or authentication, a simple read-only list retrieval is sufficiently transparent. It could include a note on static vs. dynamic data but is otherwise adequate.

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 two sentences with a list of use cases, front-loading the core function and immediately presenting the alternative tool. Every sentence adds value with no redundancy or filler.

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 no output schema and simple list return, the description covers the essential: what is returned, usage examples, and alternative for details. It could mention sorting/order of planets or missing pagination info, but for a static reference list, it is fairly complete.

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 the schema already describes both parameters (lang and compact). The description does not add extra meaning beyond the schema; it mentions the language option indirectly by saying 'Response language' but omits compact entirely. Baseline 3 is appropriate as the description does not compensate or enhance parameter understanding.

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 title and description clearly state the tool returns all 14 astrological bodies with essential meanings, specifying the fields included (name, symbol, tagline, category, ruling sign, short descriptions). It distinguishes itself from the sibling tool 'get_astrology_planet_meanings_id' which provides detailed profiles.

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 explicitly lists use cases ('astrology reference apps, planet meaning widgets, birth chart interpretation tools, astrology learning platforms') and directs users to the detailed endpoint for complete profiles, providing clear guidance on when to use this tool vs. alternatives.

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

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

No annotations provided, so description carries full burden. It describes output but omits behavioral traits like read-only nature, auth requirements, or rate limits. Given it's a GET tool, safety is implied but not explicit.

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?

Front-loaded with purpose, then details. Lists many use cases and fields. Slightly verbose but well-structured and every sentence adds value.

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 provided, so description must cover return structure. It does so thoroughly: symbol, tagline, category, temperature, orbital period, retrograde, dignities, keywords, descriptions. Also handles all 3 parameters. Complete for a lookup 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 100%, but description adds value by clarifying id accepts case-insensitive names and examples (sun, Sun, MOON), explaining compact parameter's columnar format, and confirming lang default. Adds meaning beyond 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?

Description clearly states the tool retrieves comprehensive planet interpretations, lists return fields (symbol, tagline, etc.), and distinguishes from sibling 'get_astrology_planet_meanings' which likely returns a list of planets. The verb 'retrieve' and resource 'planet interpretation' are specific.

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?

Includes use cases like 'birth chart readings, planet meaning lookups' but does not explicitly exclude other uses or contrast with siblings. Missing when-not-to-use guidance.

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

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

No annotations are provided, so the description bears full burden. It does not disclose whether the tool is read-only, safe, or has any side effects. For a simple GET endpoint, the lack of any behavioral context is a gap.

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 two sentences with a list of use cases, front-loading the main purpose. It is clear and efficient, though the list of uses could be slightly trimmed without losing value.

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?

Despite no output schema, the description fully explains what is returned (name, symbol, element, date ranges, descriptions) and mentions alternative endpoints for detail, making it complete for a list 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 100%, baseline 3. The description adds context for both parameters: explains the lang enum as ISO 639-1 and compact parameter's token-optimization benefit, surpassing the schema alone.

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 'Returns all 12 tropical zodiac signs' and lists the specific information fields, distinguishing it from sibling tools like get_astrology_signs_id which returns a single detailed sign.

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 explicitly lists use cases ('zodiac sign lists, horoscope widgets, birth chart calculators') and directs to use GET /signs/{id} for more detailed profiles, providing clear when-to-use guidance.

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

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

No annotations are provided, so the description carries full burden. It explains input requirements and return fields, but does not disclose behavioral traits like rate limits, destructive actions, or error handling. Adequate but basic for a data retrieval tool.

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 a single verbose paragraph listing many return fields. It is not front-loaded; the first sentence is clear but followed by a long, comma-separated list. Could be more concise and structured with bullet points or shorter sentences.

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 3 parameters, no output schema, and no annotations, the description sufficiently explains input validation, language support, compact mode, and return content. It lacks error handling or rate limit info, but is complete enough for its complexity.

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 covers 100% of parameters with descriptions. The description adds value by explaining the compact parameter's token optimization, language fallback behavior, and input flexibility (case-insensitive). Goes beyond schema details.

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 retrieves comprehensive zodiac sign information, specifies input format (lowercase ID or case-insensitive name), and lists returned data (element, modality, etc.). It effectively distinguishes from sibling tools that handle dynamic horoscopes or other astrological data.

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 mentions it's 'Perfect for horoscope readings, zodiac compatibility checks' etc., implying use for static sign profiles vs. dynamic horoscopes, but does not explicitly exclude other tools or provide direct comparisons. Good context but lacks explicit when-not-to-use guidance.

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

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

No annotations are provided, so the description bears full responsibility. It explains the automatic application of day/night formulas and the return of specific data points per lot. It does not mention destructive actions, authentication, or rate limits, but for a computational tool, the description is sufficiently transparent about what the tool does.

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 a single paragraph of four sentences, front-loaded with the main purpose. It is informative but includes some redundancy (listing all seven lots again). It is reasonably concise and well-structured.

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 no output schema, the description provides a clear picture of what is returned (zodiac sign, degree, longitude, arc, interpretation) for each of the seven lots. It covers the core functionality well, though missing edge cases or error handling.

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% with descriptions for all 8 parameters. The tool description adds no additional meaning beyond the schema's parameter descriptions, so baseline 3 is appropriate.

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 seven Hermetic lots (Arabic parts) for a birth moment, listing each lot by name. It uses a specific verb ('Calculate') and identifies the resource ('seven Hermetic lots'). The title and description are distinct from sibling tools, none of which are dedicated to Arabic lots.

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 implies usage for Hellenistic and traditional astrology, but it does not explicitly state when to use this tool versus alternatives (e.g., post_astrology_natal_chart). There is no mention of when not to use or of sibling tools, so guidance is minimal.

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

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

With no annotations, the description fully discloses behavioral traits: return values including tightness score, dissociate flag, interpretation, and disambiguation logic (e.g., Grand Cross suppresses T-Squares). This exceeds expectations.

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 front-loaded with the main purpose and is generally concise, though it includes some redundant phrasing. Still, it is efficient for the amount of information conveyed.

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 and no output schema, the description thoroughly explains return values, patterns, and behavioral nuances, making it complete for AI agent usage.

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 100%, so the schema already documents all parameters. The description does not add parameter-level detail, but it is unnecessary given the schema's completeness. Baseline score of 3 is appropriate.

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 identifies classical Western astrology multi-planet configurations in a birth chart, listing specific patterns like Grand Trine, Kite, etc. It distinguishes from siblings like post_astrology_aspects by focusing on patterns rather than individual aspects.

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 provides usage contexts such as personalized natal report engines and astrology chatbots, but does not explicitly state when not to use it or mention alternatives. However, the context is clear enough among siblings.

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

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

With no annotations, the description carries the full burden. It mentions 'Uses standard Western astrology orbs' but does not disclose other behavioral traits like auth needs, rate limits, or that it is a safe read-only operation. The description is adequate but could be more 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?

The description is six sentences, concise and front-loaded with the main action. It efficiently covers purpose and output without unnecessary words. Slightly more structure (e.g., bullet points) could improve scannability, but it is already well-organized.

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 absence of an output schema, the description reasonably explains what is returned (aspect type, angle, orb, status, strength) and mentions filtering options. However, it lacks details on response structure or interpretation of strength, and the sibling tool context is not leveraged for differentiation.

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. The description does not add meaning beyond the schema for each parameter. It lists aspect types in the narrative but does not elaborate on parameter values or formats beyond what the schema already provides.

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 title and description clearly state the tool calculates planetary aspects, listing major and minor aspect types. However, it does not differentiate from sibling tools like post_astrology_transit_aspects, so clarity is high but not perfect.

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 suggests the tool is 'perfect for aspect tables, transit analysis, and aspect pattern detection,' providing some usage context. But it does not explicitly state when to use this tool versus similar ones, nor does it give exclusions or alternatives.

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

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

No annotations exist, so the description carries full responsibility. It discloses that each asteroid returns zodiac sign, degree, house, daily speed, retrograde status, and interpretation. It also states what is not included (Chiron). This provides good transparency, though it could mention any error conditions or data limits.

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 two sentences, efficiently covering purpose, inputs, outputs, and exclusions. It is front-loaded with the main action and avoids any unnecessary words or repetition.

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?

With 8 parameters and no output schema, the description adequately lists return fields (zodiac sign, degree, house, speed, retrograde, interpretation). It also mentions the purpose in natal and relationship astrology. The completeness is high, though it could detail how the house system or other parameters affect output.

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 the baseline is 3. However, the description adds context beyond the schema by stating the asteroids included, that interpretations are provided, and the distinction from Chiron. This additional meaning helps the agent understand the outputs, warranting a 4.

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 natal positions of Ceres, Pallas, Juno, and Vesta. It lists specific return fields and distinguishes from the Chiron endpoint, which is available elsewhere. The verb 'calculate' and resource 'natal positions' are explicit.

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 provides clear usage context: it's for natal positions of the four asteroid goddesses, and explicitly notes that Chiron should be retrieved via the natal chart endpoint. Also mentions its use for natal reports and relationship astrology, guiding when to select this tool over others.

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

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

With no annotations, the description carries full burden. It describes the output (meridian line longitudes, rising/setting curves, interpretation) but omits details on rate limits, authentication, or error handling. Moderate transparency.

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, front-loaded with main action. Efficient but could be slightly more concise. Good structure overall.

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 no output schema, description explains return values (right ascension, etc.) and includes interpretation. Adequate for the tool's complexity, though edge cases not mentioned.

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. The description adds little beyond schema, only restating some parameter purposes. No new semantic context provided.

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 it generates an astrocartography map, listing specific planetary lines (Midheaven, Imum Coeli, Ascendant, Descendant) and what it returns. This is distinct from siblings which cover horoscopes, moon phases, and other astrology calculations.

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 explicit guidance on when to use this tool vs alternatives. The description implies its use for relocation astrology, but does not specify when not to use it or suggest better alternatives.

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

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

The description thoroughly explains what the tool returns, but there are no annotations. It does not disclose any side effects (e.g., data mutation), authentication needs, rate limits, or data persistence. Since no annotations are provided, the description carries full burden but only covers output, not behavioral context.

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 a single paragraph of about 5 sentences, front-loaded with purpose. It is fairly concise and wastes no words, but could benefit from bullet points or sections for readability. Still, it is effectively compact.

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 and the absence of an output schema, the description does an excellent job explaining the return shape: overall score, five category breakdowns with specific planetary pairs, sign compatibility narratives, element balance, archetype classification, and significant aspects with interpretations. It is very complete.

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 every parameter has a description. The tool description adds little meaning beyond that; it mentions that time determines Ascendant and that lang defaults to English, but these are already in the schema. Baseline 3 is appropriate.

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 compatibility score using Western synastry, and enumerates the outputs: overall score, category breakdowns, narratives, element analysis, etc. However, it does not explicitly differentiate from the sibling 'post_astrology_synastry', which likely provides similar inter-chart aspects without the scoring.

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 explicit guidelines on when to use this tool versus alternatives like synastry or composite chart. The usage is implied for detailed compatibility analysis with numerical scoring, but the description lacks 'use this when' or 'for raw aspects use synastry' instructions.

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

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

No annotations present, so description must cover behavior. It lists returned data (planetary positions, aspects, interpretation) but omits details about side effects (e.g., no chart saved) or authentication requirements.

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 verbose and includes redundant keywords at the end ('Composite chart API, midpoint chart calculator...') that do not add value. It could be more concise.

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?

Despite no output schema, the description specifies what the response contains (planetary positions, house cusps, aspects, interpretation). This is sufficient for an agent to understand the return structure.

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% with detailed parameter descriptions. The description adds no new parameter-level meaning beyond the schema, so baseline 3 is appropriate.

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 it generates a composite chart from two natal charts, explaining what the composite represents and what it returns. It distinguishes itself from sibling tools like synastry by focusing on midpoint relationship.

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 implies use for relationship analysis but does not explicitly compare to alternatives like synastry or compatibility score. No 'when to use' or 'when not to use' guidance is provided.

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

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

No annotations provided, so the description carries full burden. It discloses the core behavior (calculating positions, detecting conjunctions, returning interpretations) but does not mention limitations (e.g., star catalog size, response if no conjunctions) or whether it is read-only. Still, 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?

The description is about 150 words, well-structured and front-loaded with purpose and output details. Every sentence adds value, though it could be slightly more concise. It is appropriate for a specialized tool.

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 no output schema, the description thoroughly explains return values (longitude, sign, magnitude, nature, interpretations) and star selection. It also mentions the 'compact' parameter for token optimization. The coverage is complete for a focused calculation 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 description coverage is 100%, so baseline is 3. The main description adds context about which parameters are used for fixed stars, but each parameter already has a thorough description in the schema (e.g., orb with defaults, compact format explanation). The tool description does not add significant new meaning beyond the 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?

The description explicitly states the tool calculates tropical zodiac positions of named fixed stars and detects conjunctions to natal chart points. It lists specific stars (Regulus, Spica, Aldebaran, Antares, Algol) and output details (longitude, magnitude, interpretation), clearly distinguishing it from sibling tools like natal chart or aspects.

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 says it is a 'focused tool for natal reports' that weighs specific stars, implying its use case. However, it does not explicitly state when not to use it or suggest alternatives among siblings, though the context of fixed stars is clear.

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

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

With no annotations, the description carries the transparency burden. It discloses essential behavior: calculates house cusps for specified systems, returns sign/degree info, and notes time sensitivity. However, it omits error conditions, date range limits, and authentication requirements.

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 three focused sentences that front-load the core functionality, output, and key use case. Every sentence adds value with no 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?

Given the lack of output schema and annotations, the description covers the main purpose and parameters but does not describe the return format structure or potential errors. It is adequate but not fully comprehensive.

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% with detailed parameter descriptions. The tool description does not add additional semantic meaning beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 house cusps using specified systems and lists deliverables (12 cusps, Ascendant, MC). It distinguishes itself from siblings by focusing solely on house cusps, with an explicit comparison feature.

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 indicates when to use the tool (astrology charts, educational comparisons) and how to use the 'all' parameter. However, it does not explicitly mention when to prefer sibling tools like post_astrology_natal_chart for full chart calculations.

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

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

No annotations provided, so the description carries full burden. It discloses that the tool returns both mean and true apogee with detailed fields, including interpretation. As a read-only computation, no destructive behavior is expected, and the description covers the output sufficiently.

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, front-loaded with the main action, and every sentence adds value. No redundancy or 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?

Given 8 parameters and no output schema, the description adequately explains the return fields (both variants, coordinates, interpretation). It is complete enough for an AI agent to understand the tool's output without requiring an output schema.

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% with parameter descriptions, so baseline is 3. The description does not add further parameter-specific meaning beyond what is already in the schema, merely restating the overall purpose.

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 that the tool calculates Black Moon Lilith (both mean and true apogee) for a birth chart, listing specific return fields. It distinguishes itself from sibling tools like planets or asteroids by focusing on this specific astrological point.

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 implies usage for natal astrology Lilith calculations, but it does not explicitly state when to use this tool over alternatives like post_astrology_planets or post_astrology_asteroids. No exclusions or conditions are given.

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

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

With no annotations provided, the description fully discloses the tool's behavior: it projects planets, returns various data fields, and generates lines. It is transparent about the output without contradictions, though it omits notes on authentication or rate limits which are not critical for a generation tool.

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 two sentences long, front-loaded with the core function and output, followed by use cases. Every sentence earns its place with no redundancy or 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?

Given 8 parameters and no output schema, the description adequately explains the tool's purpose, output, and typical use cases. It covers the essential context for invocation, though it does not detail every aspect of the complex astrology computation (which the schema parameters handle).

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 has 100% description coverage, so the parameter descriptions are already detailed. The tool description adds global context about the output and use cases, providing meaning beyond individual parameters. This supplements the schema effectively.

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 generates a local space astrology map projecting natal planets onto the local horizon, with specific output details (azimuth, altitude, compass direction, etc.). The title reinforces this, effectively distinguishing it from sibling tools like horoscopes or transits.

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 provides clear context by stating it is ideal for relocation planning, directional astrology, and travel-direction maps. However, it does not explicitly indicate when not to use the tool or mention alternatives, which would strengthen guidance for an agent.

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

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

With no annotations provided, the description carries full burden. It explains the calculation logic (Moon returning to natal longitude) and output contents, but does not disclose potential limitations, data sources, or performance characteristics. The description is adequate but not exhaustive.

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 front-loaded with the core action, but includes redundant sentences and a trailing list of keywords (SEO-like). It could be trimmed to be more concise while retaining essential information.

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 9 parameters and no output schema or annotations, the description covers the tool's purpose and output contents but lacks details on response format, error handling, or usage limits. It is sufficient for basic understanding but not fully comprehensive.

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 has 100% parameter description coverage, so the baseline is 3. The tool description does not add significant parameter-level detail beyond what the schema already provides, such as format constraints or relationships between parameters.

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 generates a lunar return chart for monthly astrological forecasting. It specifies the exact moment of Moon return and lists output contents (planetary positions, aspects, etc.). However, it does not explicitly contrast with sibling tools like solar return, which could further clarify its unique 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 implies use for monthly emotional forecasting and Moon cycle insights, but lacks explicit guidance on when to use versus alternatives (e.g., solar return for annual forecasts). No exclusions or prerequisites are mentioned, leaving the agent with only implied context.

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

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 only mentions verification against NASA JPL Horizons but does not disclose behavioral traits like mutability, idempotency, rate limits, or authentication needs. For a POST tool this is a notable gap.

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 informative and front-loaded with the main purpose. While relatively long, each sentence adds value (list of outputs, verification, use cases). No redundant phrases.

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 description adequately covers inputs and outputs for a natal chart tool, but lacks details about the response structure. Given no output schema, users would benefit from a hint of the JSON format. The mention of 'dominant elements and modalities' is helpful.

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% with detailed parameter descriptions. The tool description adds overall context (e.g., house systems, celestial bodies) but does not provide significant new semantics beyond the schema. Baseline 3 is appropriate.

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 begins with a specific verb ('Calculate') and resource ('complete Western astrology natal chart'), and lists detailed return values (14 bodies, houses, aspects). It clearly distinguishes from sibling tools like post_astrology_houses or post_astrology_planets by emphasizing completeness.

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 provides clear usage context ('Perfect for astrology apps...') and the name/title imply this is for individual birth charts. However, it does not explicitly state when not to use this tool versus alternative sibling tools (e.g., composite chart, synastry).

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

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

No annotations are provided, so the description must cover behavioral aspects. It explains that the tool computes a return chart when a transiting planet conjuncts its natal longitude, and states that the output includes 'full tropical zodiac chart with all planetary positions, house cusps, and aspects.' This gives a clear picture of what the tool returns and the underlying logic. It does not mention side effects, but likely safe.

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 overly verbose, containing multiple repetitive sentences and marketing phrases like 'Returns full tropical zodiac chart...' and ending with a list of keywords. The first two sentences convey the core purpose, but the rest adds noise. It could be cut by half while retaining all necessary information.

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 description covers the main purpose and expected output, but given the complexity (10 parameters, 7 required, no output schema), it lacks details on how the approximateDate is used, prerequisites for birth data, or behavior when the return cannot be found. The conceptual explanation is helpful but not fully comprehensive.

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 all parameters already have descriptions in the schema. The description adds minimal extra meaning beyond the schema, such as emphasizing Saturn return as a 'major life milestone.' This is useful context but not essential for using the tool correctly. Baseline 3 is appropriate.

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 a planetary return chart for Mercury, Venus, Mars, Jupiter, or Saturn,' specifying the verb and resource. It also explains the concept of planetary returns and lists the supported planets, distinguishing it from lunar/solar returns implicitly. However, the inclusion of marketing keywords like 'Planetary return chart API, Saturn return calculator' adds clutter and slightly reduces clarity.

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 provides cycle lengths for different planets (e.g., Saturn ~29 years, Jupiter ~12 years), which helps agents decide when to use this tool based on timing. However, it does not explicitly mention when not to use it or compare with sibling tools like lunar_return or solar_return. No guidance on preferred scenarios or alternatives is given.

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

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

No annotations are provided, so the description carries full burden. It discloses what the tool calculates and returns, but does not explicitly state that it is a read-only, non-destructive operation. For a calculation tool, this is adequate but not thorough.

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 three sentences, front-loaded with the core action. It is informative without being verbose. A slight improvement could be breaking into bullet points, but current structure is efficient.

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 (14 bodies, 7 parameters, no output schema), the description is largely complete. It covers the scope, return values, and use cases. It does not mention output size or pagination, but that is acceptable for a single-response 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 description coverage is 100%, so baseline is 3. The description adds context about the returned fields (longitude, zodiac sign, etc.) but does not significantly enhance parameter understanding beyond the schema. It lists the 14 celestial bodies, which connects to the date parameter's purpose.

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 tropical zodiac positions for 14 specific celestial bodies, explicitly listing them (Sun through Pluto, lunar nodes, Chiron, Black Moon Lilith). It specifies return fields and use cases, distinguishing it from sibling tools like post_astrology_planetary_returns (which focuses on return times) by focusing on ephemeris positions.

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 provides explicit usage contexts: 'transit tracking, ephemeris tables, astrology apps, and planetary position widgets'. While it doesn't explicitly state when not to use it or compare to alternatives, the use cases are clear and help the agent decide.

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

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

With no annotations, the description explains the calculation process and output structure, including the rule of advancing rising sign by one house per year and the returned fields. It does not mention side effects or error handling, but provides adequate behavioral context.

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 two concise sentences, front-loading the purpose and technique, with no wasted words. It efficiently conveys the key information.

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 and lack of output schema, the description covers the main outputs (age, profected house/sign, lord of the year, interpretation) and explains the underlying logic, making it sufficient for an agent to understand the tool's function.

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 100%, and the tool description does not add significant meaning beyond the parameter descriptions provided in the schema. Baseline score is appropriate.

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 annual profection and lord of the year, specifying the Hellenistic time lord technique. It details the mechanism and outputs, distinguishing it from sibling tools like transits or progressions.

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 implies usage for annual profection calculations but does not explicitly state when to use this tool over alternatives like other time lord methods or transit readings. It lacks explicit usage boundaries or prerequisites.

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

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

No annotations are provided, so the description must fully disclose behavioral traits. It explains what is returned but omits any side effects, permissions, rate limits, or confirmation of whether it is read-only/mutation. The POST method implies calculation, but no safety or destructive hints are given.

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 relatively concise, front-loading the key concept and listing essential return data. The final sentence is somewhat repetitive but does not detract heavily. No unnecessary verbs or filler.

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 no output schema, the description adequately explains the return structure (progressed bodies with fields, progressed Ascendant/Midheaven via Naibod arc). It covers the main outputs but could clarify if aspects or house cusps beyond whole-sign are included. Reasonably complete for the complexity.

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% with every parameter described. The description adds overarching context (day-for-a-year key, target date explanation) but does not significantly enhance understanding beyond the schema definitions. Baseline 3 is appropriate.

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 explicitly states it generates secondary progressed charts using the day-for-a-year key, lists returned elements (progressed bodies, Ascendant, Midheaven), and highlights the progressed Sun and Moon as timing markers. This clearly identifies the tool's function and distinguishes it from sibling tools like transits or solar arcs.

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 implies use for long-term personal development by mentioning 'inner growth and emotional chapters', but it does not explicitly contrast with alternatives (e.g., transits, solar arcs, lunar returns). No direct guidance on when to prefer this tool over siblings.

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

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

No annotations provided, so description carries full burden. It discloses key behavioral traits: birth moment unchanged, planets keep signs/degrees, angles and houses recomputed. Mentions verification against NASA JPL Horizons.

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 (3 sentences) and well-structured: action statement, core principle, return data, use cases, verification. Every sentence adds value with no 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?

Given the complexity of relocation charts and lack of output schema, the description is complete. It explains the concept, return data, use cases, and verification, leaving no critical gaps for an AI agent.

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% with detailed parameter descriptions including examples and constraints. The tool description adds context beyond schema, explaining the overall logic and how parameters relate.

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 relocation chart for a new place, explains that planets retain natal positions while angles and houses are recomputed, and lists the returned data. It distinguishes from siblings by specifying the relocation aspect.

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 mentions use cases (relocation astrology readings, astrocartography move planning, travel charts) and implies when to use, but does not explicitly state when not to use or compare with siblings like astrocartography.

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

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

With no annotations, the description carries the full burden. It explains the calculation method (solar arc based on secondary progression), output format (natal and directed positions, interpretations), and that it uses tropical chart positions. It does not disclose any side effects or limitations beyond the scope, but for a calculation tool, this is sufficient.

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 a single paragraph of four sentences, each adding value: tool purpose, concept explanation, return values, and use case. It is front-loaded with the core action and no redundant information.

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 no output schema, the description adequately explains return values (solar arc, directed points with details, interpretation). It also provides context on the calculation. For a complex tool, it could mention more about limitations or precision, but it is sufficiently complete.

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 100%, so all 8 parameters are documented in the schema. The description references birth moment and target date but does not add significant new meaning beyond what the schema already provides. Baseline of 3 is appropriate.

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 solar arc directed chart for any birth moment and target date, explaining the concept and expected output. It distinguishes itself from sibling tools by focusing specifically on solar arc directions.

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 mentions it is for predictive astrology apps timing major life events, but does not explicitly state when to use this tool versus alternatives like progressions or transits. The guideline 'no astronomy expertise needed' is present but lacks contrast with siblings.

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

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

Discloses key behavior: cast for exact Sun return moment, returns full chart with positions/houses/aspects, location-sensitive. No annotations provided, so description carries full burden and does so adequately.

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 paragraph but includes keyword stuffing at the end ('solar return chart API, annual horoscope forecast...') which adds redundancy without value. Could be more concise.

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?

With no output schema, description lists return contents (planetary positions, house cusps, aspects, Ascendant, Midheaven). Covers main outcome but could mention additional details like aspects strengths or orb.

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 has 100% description coverage, so baseline 3. Description adds minimal extra value for parameters beyond the schema, except for location sensitivity context.

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 a solar return chart for any year' and distinguishes it from siblings like lunar return or natal chart by emphasizing annual forecasting and location sensitivity.

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?

Implies use for annual forecasting but lacks explicit guidance on when to choose this tool over alternatives (e.g., lunar returns, progressions). No mention of prerequisites or exclusions.

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

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

With no annotations, the description carries full burden. It discloses that it returns compatibility scores, inter-aspects, and relationship dynamics, and mentions it uses Western tropical astrology. However, it does not mention limitations (e.g., accuracy dependency on birth time) or side effects.

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 four sentences long, front-loaded with the main verb, and every sentence adds value. No wasted words, clear structure.

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 tool has nested objects and no output schema, the description adequately explains what is returned (compatibility score, inter-aspects). However, it could be more complete by mentioning error conditions or the need for accurate birth data.

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 high (all top-level and nested parameters have descriptions), so baseline is 3. The description does not add additional value beyond the schema; it focuses on the tool's purpose rather than parameter details.

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 it calculates synastry (relationship compatibility) between two natal charts, specifies the analysis (inter-chart aspects, compatibility score), and lists use cases (dating apps, matrimonial sites). It distinguishes itself from siblings by focusing on relationship compatibility.

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 provides context for when to use (e.g., dating apps, relationship counseling) but does not explicitly state when not to use or mention alternatives like post_astrology_compatibility_score. It implies usage but lacks exclusion criteria.

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

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

No annotations provided; description carries all transparency burden. It describes what the tool returns (aspect type, orb, status, interpretation, impact, guidance) and that it compares current/future positions against natal chart. However, it omits behavioral traits like read-only nature, auth needs, or rate limits, leaving some gaps.

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?

Description is moderately concise but includes redundant SEO-like keywords at the end ('Transit aspects API, transit-to-natal analysis, predictive astrology, personalized transit forecast') that add bulk without new information. Front-loads key purpose well, but could be trimmed by about 20%.

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 8 parameters, a nested input schema, and no output schema, the description provides a solid overview of both inputs (natal chart, transit date) and outputs (interpretation fields, impact rating). It explains the comparison logic and filtering support. Minor missing detail: output structure (array of aspects) is implied but not explicit.

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 100%, so baseline is 3. Description adds value beyond schema by summarizing output fields and highlighting 'AI-friendly interpretation fields', which gives context for why this tool is richer. It also mentions filtering capabilities that align with schema parameters. This extra context justifies a 4.

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 specific verb 'calculate' and resource 'transit-to-natal aspects', detailing it provides interpretations, strength ratings, and timing guidance. It explicitly differentiates from sibling 'post_astrology_transits' by stating it's 'more detailed' and includes 'AI-friendly interpretation fields', making purpose and distinction clear.

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?

Description explicitly contrasts with the /transits endpoint ('more detailed than the /transits endpoint — includes AI-friendly interpretation fields'), guiding agents to use this tool for detailed interpretations. It mentions filtering support (planet and aspect-type) but does not explicitly state when not to use or prerequisites. Clear but lacking full exclusions.

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

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

No annotations provided, so description must carry the burden. It explains return data (14 bodies, signs, degrees, speeds, aspects with orbs) and the compact parameter effect. Missing details on error handling or auth, but these are less critical for a calculation tool.

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 a concise 5-sentence paragraph with the main action front-loaded. It avoids fluff but could benefit from bullet points for scannability.

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?

With 6 parameters including a nested object and no output schema, the description sufficiently conveys the output structure (planets, aspects) and usage context. Lacks info on error states but is adequate for the tool's complexity.

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 100%, so parameters are already well-documented. The description adds no parameter-specific guidance beyond the schema, meeting the baseline expectation without additional value.

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 it calculates planetary transits and optionally compares to natal chart for aspects. It names the 14 celestial bodies returned and differentiates from sibling tools like post_astrology_transit_aspects by covering full transit positions and aspects.

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 gives usage examples (daily forecasts, aspect alerts) but does not explicitly state when to avoid this tool or compare it to alternatives like post_astrology_transit_aspects. Context is implied but not exclusionary.

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