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

The annotations already establish that this is a safe, read-only, idempotent operation. The description adds meaningful behavioral context beyond those annotations by clarifying that it does not perform birth time correction and that birth details are used only for calculation and are not stored.

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 description is front-loaded with the core purpose and avoids unnecessary wording. The opening sentence is long because it enumerates several outputs, but each clause contributes useful information and the following sentences are brief.

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?

There is no output schema, so the description appropriately explains what the tool returns in plain language: time windows until sign changes, pada and D9/D10 sensitivity, and life chapter date movement per minute. It is sufficiently complete for a three-parameter read-only calculation tool, though it could say more about when to use 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%, so all three parameters are already documented in the input schema. The description mentions birth time conceptually but does not add format, validation, or usage details beyond what the schema provides.

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 description states a precise, specific capability: it measures how sensitive the chart is to the recorded birth time, including rising sign, Moon nakshatra pada, D9/D10 rising signs, and life chapter date movement. This clearly distinguishes it from the sibling tools, which cover chart overview, chapters, birthplace lookup, life areas, and panchang.

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?

Usage is implied by the purpose: an agent would use this when birth time accuracy or chart sensitivity is in question. The description also includes a useful exclusion, stating that it does not correct the birth time, but it does not explicitly say when to choose this tool versus alternatives or what prerequisite conditions apply.

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