Varga D2: Hora

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful operational detail — POST endpoint and a 20-credit Tier 2 cost — but says nothing about computation behavior such as how the half-sign division is calculated or which defaults (Lahiri ayanamsa) apply.

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?

Front-loaded identifier plus a bracketed metadata block; every line is compact and easy to scan. The trade-off is that the budget is spent on endpoint/cost metadata instead of semantic guidance, but there is no padding or 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?

For a 13-parameter tool with low schema coverage and a rich astrological domain, the description leaves the agent guessing about ayanamsa selection, timezone handling, and which optional flags (cosmogram, zodiacType) to set. The output schema covers return values, so that omission is acceptable, but the input-side completeness is weak.

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 description coverage is only 23% across 13 parameters, so the description needs to compensate and does not. It merely restates the four required fields already marked required in the schema and adds no meaning for high-impact optional parameters like ayanamsa, zodiacType, houseSystem, or timezone, which materially change a Vedic varga result.

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?

States a specific verb-like resource (Hora/D2 varga chart) with its domain use (wealth analysis) and technical basis (half-sign Sun/Moon division), which clearly separates it from the sibling varga family (D1, D3, D7, D9...). It does not, however, explicitly contrast itself against those siblings or against wealth-oriented tools like astroway_financial_wealth_house.

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 when-to-use or when-not-to-use guidance is given. An agent must infer from 'wealth analysis' alone whether to call D2 rather than D9 or a financial-report tool, and nothing indicates prerequisite inputs beyond the four required parameters or how this differs from the other ~20 varga endpoints.

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