Expression / Destiny (kabbalistic-strict)

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

Annotations already indicate readOnly, nondestructive, idempotent. Description adds system detail but contradicts schema by implying a 'name' parameter is required. No mention of what the output contains.

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?

Description is short but includes an example with 'name' not in schema, making it incorrect. The group header is useful but doesn't offset the error.

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?

Among many siblings, no differentiation provided. Missing output schema and no explanation of what the result is. The contradictory example 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?

Schema coverage is 100%, so schema describes parameters. Description adds no semantic value and introduces a nonexistent 'name' parameter, 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?

Description states it calculates the Expression/Destiny number from full birth name letters, which is clear. However, the input schema does not include a 'name' parameter, creating confusion about the actual required input.

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 siblings like numerology_kabbalistic_strict_balance or other systems. Multiple very similar tools exist, and the description lacks differentiation.

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