Soul Urge / Heart's Desire (kabbalistic)

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds no behavioral context beyond the calculation itself, but does not contradict annotations.

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 description is short and front-loaded, but the example request body includes a 'name' key that does not match the schema, making it misleading. Concise but inaccurate.

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?

Many sibling tools (e.g., numerology_kabbalistic_strict_soul_urge) exist. The description fails to differentiate between Kabbalistic and other systems, or between 'strict' variants. Lacks completeness for an astrology/numerology domain.

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?

The description mentions a 'name' parameter in the example, but the input schema contains no 'name' property. Schema coverage is 100%, so the description misleads agents about required parameters rather than adding value.

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 the tool calculates the Soul Urge number from vowels of the full birth name, which is specific. However, it references a 'name' parameter not present in the schema, introducing confusion.

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 the many similar sibling numerology tools (e.g., Chaldean, Pythagorean, strict variants). No when-not-to-use or alternative mentions.

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