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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is fully covered without the description. The description adds a cost cue ('10 credits (Tier 1)') and the group membership, which is real value comparable to a rate-limit note, but nothing about computation semantics beyond the consonants rule.

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?

Two tightly written sentences plus bracketed metadata; the calculation and the system variant are front-loaded with no filler. Every element earns its place.

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 explained, and annotations carry safety. The description supplies the calculation basis and the exact system variant, leaving only explicit routing guidance as a gap.

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%, and the two undocumented properties (name, date) are self-evident in meaning — date even carries a regex pattern. The description adds no format or constraint detail beyond the schema; 'full birth name' is the only inferred input hint. Baseline 3 applies.

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 Personality number from the consonants of the full birth name') and pins the exact system variant ('Kabbalistic (Mathers strict)'), which is precisely what distinguishes it from the chaldean, pythagorean, vedic and non-strict kabbalistic personality siblings.

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 system label implies when this tool is appropriate versus its siblings, but there is no explicit when-to-use statement, no prerequisites, and no exclusions. Usage is inferable from the naming convention rather than stated.

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