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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and non-destructive, so the safety profile is covered. The description adds the genuinely useful computation-method detail and the 5-credit cost, but omits any note on result size, pagination or why filtering matters.

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?

Two compact sentences front-load the core identity and derivation, then the filter syntax. The bracketed [Group] and [Cost] tags are lightweight metadata rather than prose padding.

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 explained, and both real parameters are documented in the schema. The unresolved mismatch between the advertised ?index/?longitude filters and the actual schema leaves an invocation gap for a no-required-parameter tool.

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% for the two real parameters (fields, precision), so the baseline would be 3. However, the description advertises filter parameters ?index and ?longitude that do not exist anywhere in the input schema, which can mislead an agent about how to invoke the tool.

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 names the specific resource (the 72 three-letter names / Shem HaMephorash), states how it is derived (computed from Exodus 14:19-21, not table lookup) and what it returns (each with its five zodiacal degrees). That clearly separates it from siblings like astroway_kabbalah_gematria and astroway_kabbalah_sephiroth, though the phrasing is a noun phrase rather than an explicit verb.

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?

It gives a usage hint for filtering (index 1..72 or longitude 0..360) and discloses the credit cost, but never says when to choose this tool over the other Kabbalah or esoteric siblings, and offers no exclusions or prerequisites.

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