Soul Urge / Heart's Desire (pythagorean)

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

Annotations already indicate read-only and idempotent behavior. The description adds no new behavioral context (e.g., return format, error handling). The mismatch between the example and schema further obscures 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?

The description is short but includes an inaccurate example that contradicts the schema. Conciseness without correctness is detrimental.

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?

The description fails to specify that the required input is a date and location, not a name. With no output schema, it also omits what the calculation returns. For a tool in a large family, this is insufficient.

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 introduces a 'name' parameter in the example that does not exist in the schema, while the actual parameters (date, latitude, longitude, timezoneOffset) receive no semantic explanation beyond the schema itself. This is misleading.

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 states it calculates the Soul Urge number from vowels of the full birth name, which is a clear verb and resource. However, this is inconsistent with the input schema which requires date and location instead of a name, reducing clarity.

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 explicit guidance on when to use this tool versus the many sibling numerology soul urge tools (e.g., Chaldean, Kabbalistic). The group label 'Numerology — Pythagorean' provides some context but no advice on selection.

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