Expression / Destiny (kabbalistic-strict)

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds genuinely useful non-annotation detail — the credit cost (10 credits, Tier 1) and the concrete endpoint — but says nothing about determinism of the reduction, edge cases (non-Latin characters, hyphens, accents), or failure conditions.

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 core sentence is front-loaded and waste-free. The bracketed Group/Endpoint/Required/Cost block is boilerplate overhead rather than prose, though it is compact and scannable.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. What is missing is the role of the `date` parameter and any hint about strict-vs-standard Kabbalistic selection — material gaps given how densely crowded the numerology sibling set is.

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 description coverage is 0%, so the description must carry the load. It partially does for `name` ("full birth name letters, all letters, reduced"), clarifying that the birth name rather than a nickname is expected, but it never explains what `date` is for in an Expression calculation, nor its required format.

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?

States a specific verb and resource: "Calculate the Expression (Destiny) number from full birth name letters," and names the system ("Kabbalistic (Mathers strict)"). It is clear what is computed, but it never explicitly distinguishes itself from the close sibling astroway_numerology_kabbalistic_expression (non-strict) or the Chaldean/Pythagorean/Vedic Expression variants.

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 pick this Expression tool over the non-strict Kabbalistic one or the other four numerology systems' Expression tools. The only routing-adjacent information is the metadata line stating required parameters and a 10-credit cost.

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