KP Ruling Planets

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

The description accurately reflects the read-only, idempotent, non-destructive annotations and adds useful behavioral details such as returning a deduplicated list and being time-dependent on the server clock. There is no contradiction with 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 well-structured with clear sections, but the all-caps formatting and repetitive emphasis on 'no birth data' and 'no date parameter' add some redundancy. Overall it remains concise and scannable.

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 includes the key output fields, the input contract, the absence of a date parameter, and a follow-up workflow recommendation when natal confirmation is needed. It gives enough context for an agent to invoke the tool correctly without requiring additional information.

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 schema already provides 100% coverage with descriptions for lat, lon, and response_format, so the baseline is 3. The description reinforces that only lat and lon are needed and explicitly states there is no date parameter, which adds useful semantic clarity 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 computes KP ruling planets for the current instant at a given lat/lon with no birth data, and lists the specific outputs (day lord, Moon/Ascendant lord chains, deduplicated ruling_planets list). It also explicitly distinguishes this from the KP chart and prashna chart tools, making its purpose unambiguous.

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 explicitly says there is no birth data and that 'now' is implicit on the server clock, which is crucial for correct use. It also names when to use this tool versus alternatives (KP chart needs BirthData, prashna chart is for horary keywords) and provides a workflow hint to follow up with asterwise_get_kp_chart if natal confirmation is needed.

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