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

Annotations already declare readOnly=true, idempotent=true, destructive=false, so the safety profile is covered. The description usefully adds cost information ('10 credits (Tier 1)') and the system variant, but says nothing about why a name is required for a Life Path calculation or about latency/auth needs.

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?

Front-loaded with the core operation in the first clause, with group and cost metadata relegated to bracketed lines. No wasted prose, though the metered-cost block is boilerplate rather than tool-specific value.

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 annotations cover the safety profile. The gaps are the unexplained required 'name' parameter and the absence of any disambiguation from the strict Kabbalistic twin, which an agent needs to pick correctly.

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 50%: 'fields' and 'precision' are documented, while 'date' and 'name' are not. The description partially compensates by explaining the date is reduced year+month+day, but the required 'name' parameter is left entirely unexplained in both schema and description.

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') plus the input derivation rule (year+month+day, reduced) and the system (Kabbalistic/phonetic). This distinguishes it from the Pythagorean, Vedic and Chaldean life_path siblings, though it does not distinguish it from the near-identical astroway_numerology_kabbalistic_strict_life_path.

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 statement of when to choose this over the many sibling life_path variants (Pythagorean, Vedic, Chaldean, or the 'strict' Kabbalistic form). Usage is only inferable from the tool name and group label; there are no alternatives or exclusions named.

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