Soul Urge / Heart's Desire (kabbalistic-strict)

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

The description contradicts the input schema: it says calculations use the full birth name, but the schema requires only date (no name parameter). Annotations indicate read-only and idempotent, which are correct, but the description introduces a misleading behavior.

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?

Very short and includes an example, but the example is inaccurate (name field not in schema). Conciseness is undermined by misinformation.

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?

No output schema and no description of what the Soul Urge number represents or its range. The tool is part of a complex numerology domain, yet the description fails to provide essential context about the calculation or expected output.

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 100%, but the description does not explain schema parameters and instead references a non-existent 'name' parameter. The example includes 'name' which is not in the schema, actively misleading the agent.

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?

The description clearly states it calculates the Soul Urge number from vowels of the full birth name, specifying the Kabbalistic (Mathers strict) system. However, the input schema lacks a name parameter, causing confusion about what input is actually required.

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?

No guidance on when to use this tool versus other soul urge calculators (e.g., chaldean, pythagorean, or non-strict kabbalistic). The description does not differentiate among the many numerology siblings.

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