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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: a cost of 10 credits (Tier 1), the required inputs, and the HTTP endpoint. It does not mention rate limits, auth, or failure modes, so it is good but not exhaustive.

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 leads the description in one clean sentence, with metadata (group, endpoint, required, cost, alias) relegated to bracketed tags that are easy to skim. Slightly tag-heavy, but no sentence is wasted.

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 the safety profile. Purpose, system, cost, and required inputs are all present, leaving only the role of `date` and cross-tool routing as gaps.

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% (only `fields` and `precision` are described in the schema). The description usefully clarifies that `name` is the 'full birth name' whose consonants drive the result, but it never explains the required `date` parameter, which is unexplained in both places and odd for a name-derived number. Partial compensation only, so baseline 3.

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 names the system ('Kabbalistic (Mathers strict)'), which is exactly the axis separating it from the chaldean/pythagorean/vedic personality siblings and from non-strict kabbalistic. An agent can select it without opening the schema.

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?

Usage is implied by the system designation and the note that it is an alias for `astroway_numerology_kabbalistic_strict_personality`, which helps disambiguate the duplicate-tool situation. However, there is no explicit when-to-use/when-not or any statement of when to prefer a chart or full-name tool instead.

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