Find Aspect Times

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

The description adds valuable context beyond annotations by noting that retrograde loops produce multiple hits (typically three) and that each is returned. Annotations already declare readOnlyHint=true and idempotentHint=true, and the description is fully consistent with these traits, enhancing 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?

The description is well-structured: it starts with the core purpose, then explains a key behavioral detail (retrograde loops), then details the two parameter methods, and ends with an illustrative example. Every sentence provides essential information without 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?

All 8 parameters are addressed (4 required, 4 optional), with clear explanations for the two natal specification paths. The tool has an output schema (per context signals), so return values are covered. The description is comprehensive for a complex astrological query 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?

With 100% schema description coverage, the baseline is 3, but the description goes further by explaining the dual methods for specifying natal position and providing an example that maps natural language to parameters. This adds significant 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 clearly states the tool finds exact moments when a transiting body aspects a natal position, using a specific verb ('Find') and resource ('aspect times'). It distinguishes from sibling tools like find_eclipses or find_retrograde_periods by its unique focus on transiting 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 explains two ways to specify the natal position and provides a detailed example, giving clear context on how to use the tool. However, it does not explicitly mention when not to use it or contrast with alternatives like compute_transits, which could further clarify usage boundaries.

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