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

Annotations already declare this a safe, idempotent, non-destructive read, so the safety burden is lifted. The description does add non-annotation context — the endpoint, the 10-credit Tier 1 cost, and the required inputs — which is genuinely useful for planning. It says nothing, however, about return content, formatting, or any limits.

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 is front-loaded and the bracketed metadata lines are scannable and consistent (group, endpoint, required, cost). It is efficient, though arguably under-specified rather than concise; nothing in it is wasted verbiage.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile. It supplies endpoint, cost, and required inputs, but given the broad 15-parameter surface and low schema coverage, it leaves too much implied about what distinguishes this tool and how to drive its options.

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 should compensate, and it does not. Its '[Required: date, time, latitude, longitude]' line merely restates the schema's required array, adding no semantics for the many undocumented optional params (zodiacType, houseSystem, cosmogram, city, name, 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 one-line phrase 'Sign-specific spending pattern' names the resource (spending pattern) and its basis (sign), which is more than a tautology of the name. However, it is vague about the verb — it never says the tool computes/derives this from birth data — and it does not distinguish itself from close siblings like astroway_financial_career_money_style, astroway_financial_savings_tips, or astroway_financial_risk_tolerance.

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 exclusions, and no routing to alternatives among the nine financial_* siblings. The only conditional information is the bracketed required-parameter list, which is task setup rather than usage context.

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