Life Path Number (kabbalistic-strict)

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful operational context the annotations do not carry: the POST endpoint and a 10-credit Tier 1 cost, which matters for an agent budgeting calls. It adds nothing about what 'reduced' means in practice or what the result contains, so it is useful but not rich.

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 purpose is front-loaded in the first sentence, with system qualification immediately after. The bracketed metadata lines are terse and each carries distinct facts (group, endpoint, required inputs, cost) rather than padding.

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 cost/endpoint/required inputs are supplied. What remains missing is the substantive distinction from the non-strict Kabbalistic life-path sibling and any note on why 'name' is needed, which an agent choosing among hundreds of numerology tools would want.

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 0%, so the description must compensate. It clarifies that 'date' is the birth date and describes the reduction over year, month and day, which is more than the bare pattern in the schema. However, the role of 'name' in a life-path calculation is never explained, and the required-parameter line merely restates 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?

The first sentence names a specific verb and resource (calculate the Life Path number) and scopes the input (birth date, reduced), while the second pins the variant to 'Kabbalistic (Mathers strict)'. This distinguishes it from the Pythagorean/Chaldean/Vedic life-path siblings, but the description never says how it differs from the sibling astroway_numerology_kabbalistic_life_path, so the strict/non-strict boundary is left implicit.

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?

The naming of the system implies when this tool applies, but there is no explicit 'use this when...' guidance and no mention of the non-strict Kabbalistic life-path sibling or when to prefer one over the other. The metadata block gives endpoint and cost but not selection criteria.

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