Life-area timing: all areas

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely useful behavior beyond them: 100-credit Tier 4 cost, the shared-scan efficiency of batching, and that `level` is lowered to antar by default specifically to keep a six-area response small. It could still note response size or rate limits, so not a 5.

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 and dense: the scope, the batching behavior, and the level caveat all land in three short sentences. The appended Group/Endpoint/Cost block earns its space because cost tier is not visible anywhere else, though it slightly interrupts the prose flow.

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?

Output schema exists and annotations carry the safety profile, so the description needn't explain return values, and it correctly focuses on scope, defaults, and cost. Marginal gaps: no mention of the span default interaction with `fromDate`/`years` (left to schema) and no expected latency or payload-size warning for the six-area case.

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 100% and the nested body already documents `areas` defaults, `level` enum semantics, `years`, `fromDate`, and `minScore`. The description restates the `areas` list and the antar default rather than adding new meaning; the only incremental signal is the rationale that antar keeps the response small.

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 the resource precisely — all six named life areas in one call — and quantifies the relationship to the per-area siblings by saying each block equals its own /vedic/timing/{area} route. An agent can tell exactly what this returns and how it differs from astroway_vedic_timing_marriage, _career, etc., without opening the schema.

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?

Gives clear selection logic: use this for all six areas at once, or narrow via `areas`. The shared chart/dasha/transit scan sentence implicitly argues for this over six separate per-area calls, which is solid routing guidance, though it never states explicitly 'prefer this when you need more than one area' or names any sibling tool.

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