Return angle, orb, polarity (hard/soft), and meaning for an astrological aspect.
| Name | Required | Description | Default |
|---|---|---|---|
| aspect | Yes | Aspect type, e.g. 'conjunction' |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint and idempotentHint, confirming safe read-only behavior. The description adds minimal extra behavioral context—merely listing output fields. It does not disclose edge cases, error behavior, or any additional operational traits beyond what annotations convey.
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, concise sentence that is front-loaded with the action and resource. It contains no filler or redundant information—every word contributes to the description.
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 simple, single-parameter lookup tool with a detailed output schema and clear annotations, the description is adequately complete. It covers the core functionality, though it omits any mention of handling invalid input or undefined aspects, which could be considered a minor gap.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema fully describes the sole parameter 'aspect' with an example ('conjunction'), achieving 100% coverage. The description does not add further meaning or constraints beyond the schema, so it provides no additional semantic 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 the verb 'Return' and the resource 'astrological aspect', and enumerates specific outputs (angle, orb, polarity/meaning). This effectively distinguishes it from sibling tools like get_planet or get_sign, which focus on different astrological entities.
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 by stating what the tool returns, but it does not explicitly specify when to use it over alternatives or provide exclusion criteria. It relies on the name and context to signal that this is for aspects, but lacks explicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct astrological function: reference lookups (sign, planet, house, aspect), chart calculations (birth_chart, planetary_positions), transit analysis (current_transits, transit_search), progression, calendar generation, and prompt management. Even similar tools like current_transits and transit_search are clearly differentiated by scope (current vs. period-based).
Naming is largely lowercase_snake_case but inconsistent in verb usage: get_* for reference lookups, while others are noun phrases (birth_chart, planetary_positions) or arbitrary verbs (generate_calendar_events). The pattern is readable but not uniform across the set.
12 tools is well within the ideal range for a domain-specific server. Each tool covers a distinct need without redundancy, and the count feels balanced for an astrology API.
The tool surface covers the core astrological workflow: reference data (signs, planets, houses, aspects), chart generation (birth, positions), transits, progressions, and calendar events. The inclusion of prompt tools also supports interpretation, leaving no obvious dead ends.