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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that it mirrors the /interpret slash command and tolerates missing birth data, which is genuinely useful, but says nothing about output length, cost, or latency for a 'deep' interpretation. Moderate added value against a low annotation bar.

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?

Front-loads the core action and keeps to three sentences. The parenthetical example list is long but earns its place by supplying the otherwise undocumented 'topic' vocabulary. No filler or repetition.

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-value description is not required, but for a tool with 11 undocumented optional parameters the description is far too thin: an agent cannot tell what combination of birth/current/target city and date/time fields produce a meaningful result, nor how the 'system' parameter alters the interpretation.

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 0% across 11 parameters, so the description carries the full burden. It enumerates valid 'topic' values (career_and_vocation, relationships, dasha_analysis, wealth_and_finance, health_and_vitality) but leaves city, date, time, system, birth_city, birth_date, birth_country, target_city, current_city, and user_prompt entirely unexplained, including the distinction between birthplace and target/current city.

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?

States a specific verb (get) and resource (personalized astrological interpretation) scoped to canonical life pillars, with concrete topic examples. It does not, however, differentiate itself from the sibling ask_astrology_guidance, whose name suggests overlapping intent, so an agent cannot fully disambiguate without opening schemas.

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?

'Can be run with or without specific birth details' gives one useful precondition, and the slash-command mapping gives context. But there is no when-to-use/when-not guidance and no routing against ask_astrology_guidance or get_horoscope, leaving selection largely implied.

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