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

The annotations already declare the full safety profile (read-only, idempotent, non-destructive), so the description's remaining burden is light. It does add genuinely useful operational context — the POST endpoint and a 10-credit Tier 1 cost — but says nothing about latency, caching, or how the safeguards are derived.

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 one-line purpose is front-loaded and the bracketed metadata is compact and scannable. Nothing is padded, though the cost/endpoint lines are administrative rather than descriptive.

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?

An output schema exists so return values need not be explained, but for a 15-parameter tool with 33% schema coverage and a doppelgänger sibling, the description leaves real gaps: no parameter semantics, no sibling disambiguation, and no usage context. The cost note is the only substantive addition.

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 would need to compensate and it does not. Its '[Required: date, time, latitude, longitude]' line merely repeats the schema's required array, adding zero meaning for the other eleven parameters (city, name, cosmogram, zodiacType, houseSystem, ayanamsaId, 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 description names a specific deliverable — an element-derived risk tolerance reading plus recommended safeguards — which is more than a restatement of the title 'Risk Profile'. It stops short of distinguishing itself from the near-identical sibling astroway_financial_risk_tolerance, so an agent must guess which risk tool applies.

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 or when-not-to-use guidance and no named alternative, despite sibling tools like astroway_financial_risk_tolerance and astroway_business_expansion_timing living in the same decision space. The bracketed Required list tells the agent what to supply, not when to reach for this tool.

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