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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description usefully adds the cost (10 credits, Tier 1), which annotations do not carry, but says nothing about computation behavior or inputs beyond the vowel basis.

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 front-loaded sentences carry the core purpose immediately, followed by compact bracketed group/cost metadata. No filler, appropriately sized for the tool's scope.

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 annotations cover safety. However, the required date parameter is unexplained for what is otherwise a name-based vowel calculation, and the strict-vs-non-strict distinction is left implicit, leaving minor 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 coverage is 50%: fields and precision are documented in the schema, but name and date are not. The description adds meaning to name ('full birth name', vowels only), but leaves the required date parameter unexplained, so it only partially compensates for the coverage gap.

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 (Soul Urge number), input basis (vowels of the full birth name), and the exact system variant (Kabbalistic, Mathers strict). This clearly distinguishes it from the chaldean/pythagorean/vedic siblings. It does not explain what separates 'strict' from the plain kabbalistic sibling, but the naming is precise enough for selection.

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 but offers no when-to-use guidance or explicit alternatives among the dozens of numerology siblings (e.g., when to pick strict over non-strict kabbalistic). Usage is only implied by the system label.

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