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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds only the credit cost (10 credits, Tier 1) and tradition grouping, which is mildly useful but says nothing about what the calculation produces or any constraints.

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?

It is short, but that brevity reflects under-specification rather than economy: two fragments of metadata and no front-loaded statement of purpose. No sentence explains the tool's operation.

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 15-parameter chart calculation with four required inputs, the description leaves the agent with no idea what is computed, what the output contains (an output schema exists but its meaning is never framed), or when to reach for this tool rather than its many Hellenistic siblings.

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 coverage is only 33% across 15 parameters, and the description contributes zero parameter meaning – it never mentions date, time, location, ayanamsa, house system, or the compact-mode fields. With low coverage, the description is expected to compensate and does not.

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 is a noun fragment, 'Constellations beyond the zodiac,' with no verb and no indication of what the tool actually computes or returns. It restates the domain of the title rather than stating an action, so an agent cannot distinguish it from siblings like astroway_helg_sphaera_barbarica or astroway_aspects_fixed_stars_catalog.

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 when-to-use guidance, no prerequisites, and no mention of any alternative tool. The only additional text is group/cost metadata, which does not help select this tool over the near-identical astroway_helg_sphaera_barbarica sibling.

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