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 the pricing tier ('10 credits, Tier 1'), which is genuinely useful context not present in annotations, but says nothing about what is computed, what is returned, or what inputs are required.

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?

Two short lines with no padding and the purpose line is front-loaded before the metadata tags. However, brevity here comes at the cost of substance rather than from efficient expression, so it is only minimally acceptable.

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 only 33% schema coverage, this description is far too thin: it omits the required birth-data inputs, the meaning of the many optional chart settings, and any differentiation from the other financial tools. An output schema exists, so return-value detail is not required, but the invocation-side gaps remain.

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 carries a heavy compensation burden and delivers nothing. It never mentions the required birth data (date, time, latitude, longitude), nor explains city, name, cosmogram, zodiacType, houseSystem, or ayanamsaId, which are undocumented in the schema as well.

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 ('Sign-specific spending pattern') essentially restates the tool name and title without a verb, scope, or output indication. It does not distinguish this tool from the many sibling financial tools (astroway_financial_career_money_style, astroway_financial_wealth_house, astroway_financial_risk_tolerance, astroway_financial_savings_tips), leaving an agent unable to tell which to pick.

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 at all: no prerequisites, no conditions, and no mention of alternative financial tools. The only extra text is group/cost metadata, which does not tell an agent when this tool is the right choice.

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