Upagrahas: Dhuma to Upaketu, Kala to Gulika, Mandi

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds operational facts such as the POST endpoint, 20-credit cost, and required date/time/latitude/longitude, but does not describe rate limits, output structure, or error behavior beyond what annotations and schema provide.

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 first sentence is front-loaded and identifies the subject, but the remainder is a dense paragraph of BPHS verse citations and formulas that do not help an agent invoke the endpoint. It is technically rich but not concise for a tool description.

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 13-parameter Vedic calculation endpoint with an output schema, the description covers astrological definitions and required inputs but omits usage guidance and most optional-parameter semantics. It is therefore not complete enough for reliable invocation despite the annotations and output schema covering safety and returns.

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?

With 13 parameters and only 23% schema-description coverage, the description needed to define the optional inputs. Instead it only lists the four required parameters and gives no meaning for ayanamsa, timezone, timezoneOffset, zodiacType, houseSystem, and others; the astrological formulas do not explain parameter usage.

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 opening "The upagrahas of BPHS ch. 3" names a specific resource, and the enumeration of Dhuma through Gulika/Mandi makes the tool's domain unmistakable. It lacks an explicit action verb and does not name a sibling, so it is clear but not fully self-differentiating.

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?

No sentence states when to choose this tool over other Vedic endpoints or when not to use it; the description is a technical definition rather than routing guidance. Usage is only implied by the subject matter.

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