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

The annotations already declare the full safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the description only needs to add context. It does add one genuinely useful trait not available elsewhere: a cost of 10 credits (Tier 1) and the HTTP endpoint. It says nothing about how the suitability judgment is produced, whether timezone/location materially affect the verdict, or what limits 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?

The purpose sentence is front-loaded and the bracketed metadata block is scannable. The [Required: ...] line duplicates the schema's required array and could be dropped, but overall there is no padding or filler prose.

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 tool that is read-only and mathematically deterministic, the description covers the essentials: what it computes, where it is hosted, and what it costs. The gaps around how a date is scored or when to prefer it over a muhurta or Tong Shu sibling are minor against annotations and an output schema that already carry the return-shape burden.

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 15 parameters and only 33% schema description coverage, the description needs to carry weight, but it only restates the four required fields already flagged in the schema's required array. It adds no meaning for the undocumented parameters (zodiacType, houseSystem, cosmogram, ayanamsaId, city, name), and it references a 'venture type' concept that has no corresponding parameter at all, which could mislead an agent into searching for a field that does not exist.

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 names a concrete resource (a proposed launch date) and a concrete judgment (suitability for a venture type), which is enough to separate it from chart-rendering siblings like astroway_western_chart. It is a noun phrase rather than a verb phrase, and 'venture type' is not an actual parameter of the tool, so the purpose is clear but slightly imprecise.

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?

Usage is implied: you supply a candidate date/place and get a suitability verdict, which tells an agent the tool is for evaluating a date rather than generating a report. However, no alternatives are named, and no condition distinguishes this from close siblings such as astroway_vedic_muhurat_business_start, astroway_business_expansion_timing, or astroway_chinese_tong_shu_select.

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