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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuinely useful operational detail beyond annotations: the credit cost (10, Tier 1), the endpoint, and required inputs, which help an agent budget and call correctly.

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?

Purpose is front-loaded in the first sentence, with structured bracketed metadata following. Nothing is wasted, though the bracket lines are slightly boilerplate-heavy relative to the terse core sentence.

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 and rich annotations are present, so return values and safety need not be described. The main gap is differentiation from the extremely crowded sibling set (kabbalistic vs kabbalistic-strict vs other systems), which the description only partially addresses via the system label.

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 50%: 'fields' and 'precision' are documented in the schema, while 'date' and 'name' are self-explanatory given their pattern/length constraints. The description only restates the required params and the date semantics, adding little beyond the schema, so the baseline 3 is appropriate.

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 ('Calculate'), resource ('Life Path number'), and the algorithm/system ('Kabbalistic (Mathers strict)') plus the input basis ('birth date... reduced'). This distinguishes it from the chaldean/pythagorean/vedic life-path siblings, though it does not explain how 'strict' differs from the non-strict kabbalistic_life_path sibling.

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 explicit when-to-use or when-not-to-use guidance, and no routing among the ~80 sibling numerology tools. Usage is only implied by the system label in the title/name. It does supply operational context (required params, cost) which is mildly helpful but not usage guidance.

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