Panchang — Hora

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 that it uses 'Chaldean order' and includes 'sunrise/sunset and day ruler', which provides behavioral context beyond annotations. The cost mention (50 credits) is also helpful. No contradictions with 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 very concise at two sentences plus example, front-loading the core purpose. However, it lacks structural elements like sections or a clear summary of required parameters. Still, every sentence adds value with no 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?

Given 11 parameters, many optional and non-obvious (e.g., 'houseSystem', 'cosmogram'), the description fails to provide sufficient context. There is no output schema, and the description does not explain what the returned data looks like or how to interpret the horas. A more complete description would benefit the agent.

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 0% schema description coverage, the description must compensate but fails to do so. It only provides an example request body without explaining any parameter meaning or constraints. Fields like 'houseSystem', 'zodiacType', 'ayanamsaId', and 'cosmogram' are left undefined, which is problematic for correct invocation.

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 it returns '24 planetary hours per Chaldean order, with sunrise/sunset and day ruler'. This verb+resource combination is specific and distinguishes it from sibling panchang tools like 'vedic_panchang_full'. However, it does not explicitly mention that the tool requires a date/time and location, though that is implied by the required parameters.

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?

No guidance is provided on when to use this tool vs alternatives such as 'vedic_panchang_choghadia', 'vedic_panchang_karana', etc. The description lacks explicit context for selection, leaving the agent to infer based on the name 'Hora' alone.

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