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

Annotations already declare readOnly/idempotent/destructive=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the credit cost (10 credits, Tier 1) and the concrete endpoint, which an agent can use for budgeting. It stops short of describing the response, but that is less critical here.

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 a single clear sentence, with metadata (group, endpoint, required, cost) cleanly bracketed afterward. Slightly label-heavy, but nothing 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 the annotations carry the safety profile. The description covers purpose, system, endpoint, required inputs, and cost. The main gap is the absence of any guidance on choosing between the many near-identical sibling personalities.

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 only 50%; 'fields' and 'precision' are documented in-schema but 'name' and 'date' are not. The description partly compensates by clarifying that 'name' is the full birth name and that only consonants are used, plus listing the required inputs, but it adds nothing about the compact-mode parameters. 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 ('the Personality number'), input derivation ('from the consonants of the full birth name'), and system ('Kabbalistic (phonetic)'). This is enough to distinguish it from the many sibling personality tools (chaldean, pythagorean, vedic, kabbalistic_strict) without opening their schemas.

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 description identifies the system and the required inputs but offers no explicit when-to-use, when-not, or alternative routing (e.g., vs. kabbalistic_strict_personality or pythagorean_personality). Usage is only implied by the group label and name.

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