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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description adds genuine behavioral context by disclosing that numerology is 'labelled modern, not classical' and by distinguishing which checks require a full chart versus date alone — useful framing an agent cannot get from 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?

The core action is front-loaded and every sentence carries information, but the opening sentence is a dense run-on packing five distinct analyses together. It is appropriately sized for the tool's complexity with only mild structural looseness.

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 not be described, and the description adequately frames the domain and the classical-versus-modern split. For an 11-parameter tool it is largely complete, though the thin parameter coverage leaves some input details to 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 27%, so the description must compensate. It clarifies the role of date/time/place and name/spellings, but says nothing about latitude, longitude, timezone, timezoneOffset, variantLimit, or when generateVariants applies, leaving roughly half the parameters' semantics unaddressed.

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 specific verb+resource with unusual precision: it checks a name's first syllable against the Moon's birth nakshatra pada (Avakahada rule) and scores it with Chaldean/Pythagorean/Cheiro numerology. An agent can distinguish this from siblings like analyze_nakshatra_profile or calculate_devata_profile purely from this text.

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?

It gives concrete input guidance ('Give date, time and place for the chart-based checks; date alone gives birth numbers only'), which tells the caller what to supply for which depth of analysis. It does not, however, tell the agent when to prefer this over a sibling tool or when it is inapplicable.

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