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

The annotations already provide readOnlyHint= true and destructiveHint=false, so the safety profile is covered. The description adds substantive behavior beyond that: it specifies the BPHS Shodasha Varga reference system and reveals that Vargottama planets are detected, which is a derived behavioral detail not present in the schema or annotations.

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?

Well front-loaded with the primary purpose in the first sentence. The second sentence lists life areas comprehensively, which is valuable for mapping intents to a division, though it partially repeats the schema's division parameter description. The last sentence about BPHS and Vargottama is brief and earns its place.

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 complex 10-parameter tool with no output schema, the description is adequately complete: it covers what the chart is, what divisions exist, what each reveals, the source system, and a special detection (Vargottama). It does not describe the return object shape in detail, but for a read-only calculation tool this is enough to correctly select and invoke 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 100% with detailed explanations for all 10 parameters, so the baseline is 3. The description does add useful domain context by explaining divisional charts conceptually and mapping D2 through D60 to life areas, which reinforces the 'division' parameter, but it does not add new parameter-level semantics beyond the schema.

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?

省Starts with a specific verb 'Calculate' and clearresource: 'any Vedic divisional chart (Varga) from D2 Hora to D60 Shashtiamsa'. It distinguishes itself from sibling tools like birth chart/navamsa by covering the entire varga family and explicitly listing the life areas each division addresses. No ambiguity about what the tool does.

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?

States exactly when to use this tool: when a Vedic divisional/varga_chart is needed, and enumerates life areas so an agent can infer the right division (e.g., wealth→D2, marriage→D9, career→D10). It does not explicitly name alternatives to use instead (e.g., 'use birth_chart for D1'), which is a minor gap, but the context is clear.

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