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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation facts: the HTTP endpoint, the 10-credit Tier 1 cost, and the required inputs. No contradiction with the read-only annotation (POST can be a non-mutating compute endpoint). It stops short of describing anything about the computation itself.

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 text is short and the key phrase is front-loaded with metadata block after, so nothing is padded. However it is under-specified rather than genuinely economical — the bracketed tags function as boilerplate, and the brevity reflects missing content more than disciplined editing.

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 tool with heavy astrological configuration options, this is thin. The output schema exists so return values need not be re-explained, but nothing tells the agent which optional parameters matter or how the four required inputs drive the result, leaving a large gap against the tool's actual complexity.

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 must compensate and does not. Its only parameter content is the required list (date, time, latitude, longitude), which merely repeats the schema's required array, while the meaningful optional controls (ayanamsa, zodiacType, houseSystem, timezone) get no explanation in either place.

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?

'Gematria-style number set per sign' names a resource and a rough method, so an agent can tell this computes sign-linked numbers rather than a full chart. But it never states the operative verb explicitly and does nothing to separate it from the many adjacent financial siblings (astroway_financial_lucky_day) or the numerology/gematria family (astroway_kabbalah_gematria, astroway_numerology_*). Purpose is decipherable but vague at the edges.

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, when-not-to-use, or alternative routing anywhere in the text. The only guidance is the '[Group: Financial Astrology]' tag and the required-parameter list, neither of which tells an agent why it should pick this tool over astroway_financial_lucky_day or the gematria tools.

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