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 genuinely useful non-annotation context — the credit cost (20 credits, Tier 2) and the Vedic grouping — but says nothing about what birth data is required, how ayanamsa choice affects the result, or how expensive calls should be batched.

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?

Two short lines, purpose front-loaded before the metadata tags, with no filler. It is efficient, though the extreme brevity is partly under-specification rather than pure economy.

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 values need no explanation, and the domain keywords give the agent its main selection signal among the varga siblings. What is missing is anything about required birth data, ayanamsa/zodiac defaults, or the cost/rate implications of calling many varga tools, which matters given 15 inputs and a 20-credit price.

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 15 parameters and only 33% schema description coverage, the description is the only place that could compensate and it contributes nothing — no mention of date/time/latitude/longitude requirements, the ayanamsa default, or the compact-mode fields/precision options. Several parameters (city, name, cosmogram, zodiacType, houseSystem, ayanamsaId) are undocumented in both places.

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?

Names the specific artifact (Chaturthamsa / D4 chart) and its classical significations (fortune, fixed assets, real estate), so an agent knows what it produces. It does not, however, say anything that distinguishes it from the fifteen sibling varga tools beyond the implicit 'D4' in the name — no explicit contrast with D1/D9/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?

There is no when-to-use statement, no prerequisites, and no routing against the dense sibling set of varga/divisional tools. The parenthetical significations only weakly imply the topical context (property questions), which is inference rather than guidance.

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