get_solar_return

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

Discloses that it computes a specific astronomical event (exact time of Sun's return) and that chart location defaults to birth place if not provided. No annotations exist, so description carries full burden. Does not mention any side effects, permissions, or rate limits, which is acceptable for a compute-only 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?

Single sentence that is front-loaded with the key purpose and then adds additional detail about location. No wasted words; every part of the sentence is informative.

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, and the description does not indicate what the tool returns (e.g., chart details, time of return, planetary positions). For a tool with 8 parameters and no output description, the completeness is lacking. The description covers input but not 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?

Input schema has 100% coverage with descriptions. The tool description adds minimal extra meaning beyond confirming that date/time/lat/lon are natal and returnLatitude/returnLongitude are for the return location. With full schema coverage, baseline is 3; description does not significantly 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?

Description clearly states it calculates the exact moment of solar return (Sun returning to natal longitude) and the chart for that moment. Uses specific verb 'calculates' and resource 'solar return chart'. While it doesn't differentiate from sibling tools, the purpose is clear and distinct from other astrological tools like get_planet_positions or get_natal_chart.

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 usage context: for a given year, using birth data and optionally residence location for calculation. However, no explicit guidance on when to use this vs siblings (e.g., when to use solar return vs secondary progressions). No exclusions or alternatives mentioned.

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