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

No annotations are provided, so the description carries the full burden, and it does substantial work: it discloses the AI/non-template nature, the internal pipeline (full chart computation, yogas, dashas, transits, dignity, house lords), multi-paragraph output, domain routing, and a licensing/usage policy restricting resale and requiring attribution. It stops short of disclosing latency, determinism, or rate/cost characteristics that an agent weighing an expensive AI call would want.

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?

Heavily front-loaded with clear labeled sections (WHEN TO USE, WHAT IT DOES, RETURNS, USAGE POLICY, NEXT) that map directly to the agent's decision. It is longer than strictly necessary, and the licensing paragraph is more contract language than invocation guidance, but the structure keeps it navigable.

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 10-parameter AI interpretation tool with no annotations and an existing output schema, the description covers purpose, triggering conditions, internal behavior, domain routing, output shape, policy constraints, and fallback siblings. An agent has everything needed to decide whether and how to call it.

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%, so the description must compensate across 10 parameters. It usefully enumerates the valid domain values (career, relationships, health, finance, education, travel, property, general) which the schema leaves as a bare string, but it says nothing about the birth-data parameters (year/month/day/hour/minute, latitude, longitude, timezone_offset) or their formats and India-centric defaults.

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 and resource ('Ask an in-depth, chart-aware astrological question') and immediately differentiates itself as 'AI-powered, not template-based'. It also names the sibling tools it is not (calculate_birth_chart for raw data, ask_prashna for yes/no horary), so an agent can route without opening either schema.

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 WHEN TO USE block defines the triggering condition precisely ('open-ended question about their life, chart, or future that needs deep Vedic interpretation'), and the NEXT block explicitly names alternatives and their use cases. Exclusions ('not a simple lookup table or template prediction') are stated up front.

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