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

Annotations cover safety (readOnly, idempotent, non-destructive), so the bar is lower. The description adds cost transparency ('10 credits (Tier 1)') and system/group labels, which are genuinely useful behavioral facts not in annotations. It does not disclose anything else beyond that.

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?

Front-loaded with the operation and system, followed by compact metadata blocks and the alias note. Nothing wasted, though the bracketed metadata lines are somewhat boilerplate.

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?

Output schema exists, so return-value explanation is unnecessary. Cost, system, and group are covered. What's missing is why an agent should pick this tool over its lookalike sibling and the strict/regular kabbalistic distinction — meaningful in a context with both astroway_numerology_kabbalistic_balance and astroway_numerology_kabbalistic_strict_balance.

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 50% — 'date' and 'name' have no schema descriptions, only format constraints, while 'fields' and 'precision' are documented. The description mentions 'initials of each part of the full name', hinting at how 'name' is consumed, but adds nothing about date format or the required date's role. Baseline 3 given the 50% coverage.

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 Balance number from initials of each part of the full name') and names the system. However, in a family of ~70 sibling tools including a near-identical astroway_numerology_kabbalistic_strict_balance, the description doesn't explain how this differs from that twin beyond the alias callout.

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 when-to-use or when-not-to-use guidance. The only routing hint is the parenthetical that this is a 'cursor-friendly alias' for astroway_numerology_kabbalistic_strict_balance, which is a naming note, not usage guidance. Alternative Balance systems (Chaldean, Pythagorean, Vedic) are not compared.

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