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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered structurally. The description adds genuinely useful operational context the annotations do not carry: the POST endpoint, the 10-credit Tier 1 cost, and the required input pair. It stops short of describing the response, but that is covered by the output schema.

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?

One front-loaded functional sentence followed by compact bracketed metadata blocks for group, endpoint, required inputs and cost. Nothing is padded, though the metadata bracket repeats 'kabbalistic' already implied by the title.

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 cost/endpoint/required inputs are present. However, the unexplained meaning of `date` and the silence on the non-strict vs strict kabbalistic distinction leave real gaps for a tool with four parameters and many near-identical siblings.

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%: the `fields` and `precision` compact-mode parameters are already documented in the schema, while `name` and `date` carry no descriptions. The description adds only that `name` is the full name whose initials are used; it never explains what role `date` plays in a 'balance' calculation. Baseline 3 is appropriate given the schema does part of the work.

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 Balance number from initials of each part of the full name,' and pins the system as Kabbalistic (phonetic). It is clearly distinguishable from the Chaldean/Pythagorean/Vedic balance siblings, but it never addresses serial variants like astroway_numerology_kabbalistic_strict_balance, so the sibling differentiation is incomplete.

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?

There is no when-to-use guidance, no statement of when to prefer this over the strict or other-system balance tools, and no preconditions beyond the required-parameter list. The agent is left to infer selection purely from the tool name.

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