get_lagna_transitions

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

With no annotations provided, the description carries the full disclosure burden. It usefully states that output is JSON, the tracking window runs from sunrise to next sunrise, timezone is derived when omitted, and multiple astronomical systems are supported. It does not cover error behavior or coordinate precedence, but these are secondary for a read-only 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?

Two sentences deliver the core behavior first, then compactly summarize all key arguments and defaults. There is no filler or repetition of schema fields, and every clause adds useful 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 is reasonably complete for a read-only astrological calculation, especially since an output schema exists for return values. The main gaps are not explaining whether latitude/longitude truly overrides the required city field, and not clarifying the practical differences between the three supported systems.

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 description adds substantial parameter meaning beyond the empty schema coverage: it documents the YYYY-MM-DD date format, city name usage, the latitude/longitude alternative, timezone derivation, and the drik|surya_siddhanta|vakya system choices with default. However, it conflicts with the input schema by implying latitude/longitude can replace the required city parameter, which is confusing for an agent deciding what to pass.

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 Ascendant (Lagna) sign boundaries for a date and city, with a specific temporal scope of sunrise to next sunrise. It is unambiguous about the resource and output format, though it does not explicitly name sibling tools to distinguish itself from 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?

The intended use is implied by the description: you call this when you need Lagna transition boundaries for a given date and place. However, there is no explicit guidance about when to choose this tool over related siblings like get_rashi_ingresses or get_graha_positions, and no exclusion criteria are provided.

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