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 that the framework is "deterministic" and that output names houses, Karakas and timing triggers, which is genuine added context, but it says nothing about latency, failure modes, or question length 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?

Three sentences, front-loaded with the core capability, but marketing language ("authentic," "direct CTA to explore the full chart on ERUX") consumes space without helping an agent decide or call correctly.

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 the description need not explain return values, and annotations cover the safety profile; for a one-parameter tool this is close to sufficient. The remaining gap is sibling differentiation, which matters here because five adjacent astrology tools exist.

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% for the single required `question` parameter, so the description must carry the load. The listed life-question categories (career shift, relationship milestones, financial timing) do help an agent phrase a valid question, but there is no guidance on phrasing, scope, or whether free-form text is expected.

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 verb+resource ("Provide ... astrological framework guidance for any life question") and enumerates the domain (career, relationships, finance, health, relocation). It never distinguishes itself from siblings like get_interpretation or get_horoscope, so an agent cannot tell from the text alone which of these 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?

The example question categories imply when this tool is appropriate, and the mention of the /ask slash command ties it to a known user gesture. However, there is no explicit when-not guidance and no routing against the five sibling tools, so the agent must infer selection.

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