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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description usefully adds cost (10 credits, Tier 1), the group and the POST endpoint, but says nothing about rate limits, latency, or what the 'archetype' output actually contains.

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 single-sentence description is front-loaded and the bracketed metadata is compact and scannable, with no filler. It is efficient, though the metadata block is boilerplate rather than explanatory content.

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?

An output schema exists, so return values need no prose, but for a 15-parameter tool with only 33% schema coverage and no usage guidance, the description is too thin. An agent cannot tell from this text when the tool applies or how the many optional chart parameters affect the result.

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 33% across 15 parameters, so the description is expected to compensate — and it does not. It merely restates the four required parameters already declared in the schema (date, time, latitude, longitude) and adds no meaning for the 11 optional ones (ayanamsa, zodiacType, houseSystem, fields, precision, etc.).

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 identifies the resource (a long wealth cycle) and its basis (Jupiter ~12y and Saturn ~29y returns), which is more informative than the bare title. However, it is a noun phrase with no verb — it never states that the tool computes/returns a wealth-cycle forecast — and it does not distinguish itself from nearby siblings such as astroway_financial_wealth_house or astroway_family_saturn_return_cycles, which also involve Saturn returns.

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?

There is no guidance on when to use this tool versus the many other financial and cycle tools (market_timing, wealth_house, planetary_cycles). The bracketed metadata gives group, endpoint, required fields and cost, but never a use case, trigger, or exclusion.

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