Find Sign Ingresses

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the tool is safe. The description adds behavioral details: retrograde crossings are flagged, Sun's Aries ingress is the March equinox, and ingresses mark astrological seasons. This context enriches understanding beyond the 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?

The description is concise with two short paragraphs and two examples. It front-loads the core purpose and uses examples effectively. Minor improvement could be more structured formatting, but it's efficient and readable.

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 an output schema (not shown but stated) and moderate complexity, the description covers the essential: what it does, retrograde handling, and usage examples. It is sufficient for an agent to select and invoke the tool correctly.

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 descriptions cover 100% of parameters, but the description adds practical meaning with examples (e.g., body: 'Saturn', from_datetime: '2026-01-01'). The examples clarify how to format dates and choose bodies, which the schema alone does not fully convey.

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 finds when a body crosses sign boundaries (ingresses) in a date range, with specific verb 'find' and resource 'sign ingresses'. It distinguishes from sibling tools like find_retrograde_periods and get_planet_position by focusing on sign changes.

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 through examples (e.g., 'When does Saturn change signs in the next 3 years?') and implicit alternatives (e.g., retrograde crossings are flagged, distinguishing from find_retrograde_periods). However, no explicit when-not or direct comparison to siblings is given.

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