Soul Urge / Heart's Desire (chaldean)

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

Annotations already declare readOnly and idempotent hints. The description adds no behavioral context beyond the basic operation. It does not describe output format or any side effects.

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?

Brief description with one sentence, group label, and example. However, the example introduces a parameter not in the schema, reducing clarity. No wasted words, but structure is flawed due to inconsistency.

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?

Does not explain what the tool returns (only says it 'calculates'). With no output schema, the description should describe the result. The parameter mismatch further reduces completeness.

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 example request includes 'name' which is not in the input schema, while the schema lists date and location parameters that seem irrelevant for a name-based calculation. This mismatch severely undermines understanding of required inputs. Despite 100% schema description coverage, the description misleads by showing an undocumented parameter.

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 using the Chaldean system. It is specific and includes a group label, though it does not differentiate from sibling numerology tools.

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 alternatives. The example shows a request but does not explain selection criteria among many similar numerology tools.

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