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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine operational context the annotations lack: the endpoint, the four required inputs, and a per-call cost of 20 credits (Tier 2). It says nothing about response shape, precision of results, or failure modes.

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-loaded with the purpose in the first clause, then a compact bracketed metadata block. Every line carries information and there is no filler, though the bracket format is terse rather than prose-explanatory.

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?

The output schema means return values need no explanation, and the description covers identity, endpoint and cost. But for a 15-parameter tool at 33% schema coverage, the description leaves too many chart-configuration choices unexplained for an agent to call it confidently without reading the schema.

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 coverage is only 33%, so the description would need to carry real weight, but it merely restates the four required parameters already flagged in the schema. The many non-obvious options (ayanamsa vs ayanamsaId, zodiacType, houseSystem, cosmogram, name/city) get no explanation here, and the description does not clarify which of these matter for a D30 computation.

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-resource pair (Trimsamsa/D30 varga chart) and names the computational variant ('Parashara unequal-segments formula'), plus the interpretive domain ('misfortunes, evils'). It distinguishes itself from the many sibling varga tools by the explicit D30 identifier, though it doesn't say how to choose it over D9 or D60.

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 'misfortunes, evils' gloss implies the astrological use case, which is more than nothing, but there is no explicit when-to-use, no comparison to sibling vargas, and no guidance on prerequisites such as choosing an ayanamsa or house system for a divisional chart.

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