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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds cost (10 credits, Tier 1), the endpoint, and required fields — useful operational context — but says nothing about the return payload's character beyond what the output schema implies.

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 purpose sentence is front-loaded and the bracketed metadata (group, endpoint, required, cost) is scannable and compact. Slightly boilerplate-heavy but nothing is wasteful.

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 annotations cover the safety profile. However, given ~11 sibling system variants of the same operation, the description omits any routing guidance, which is the main gap an agent would need filled.

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 50%: 'fields' and 'precision' are documented in the schema, but 'name' and 'date' have no schema description. The description partially compensates by specifying that date is the birth date (year+month+day, reduced) and that name and date are required, but it never explains what 'name' contributes to a date-only life-path calculation.

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 and resource ('Calculate the Life Path number from birth date') and tags the Vedic system, which distinguishes it from the chaldean/kabbalistic/pythagorean life_path siblings. It does not explain how the Vedic computation actually differs from those systems, but the naming and group tag are enough for an agent to disambiguate.

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?

No guidance on when to choose Vedic over the many sibling systems (chaldean, kabbalistic, pythagorean, numks), nor any exclusions or prerequisites beyond the required-parameter list. The agent is left to infer selection purely from the system name.

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