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

Annotations already declare this as a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description adds genuinely decision-relevant context not present in structured fields: the endpoint, the required inputs, and a billing cost of 10 credits (Tier 1), which an agent should weigh before calling.

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 carries no filler, and the bracketed metadata lines are structured rather than prose padding. The metadata block is slightly redundant with the schema's required list, but the format is scannable and cheap.

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 cost/endpoint/required inputs are supplied. What is missing is the differentiation and selection logic an agent needs when eleven near-identical Balance siblings are available, particularly the strict/non-strict boundary.

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 only 50%: `fields` and `precision` are documented in the schema, while `date` and `name` carry no schema description. The prose clarifies that `name` supplies initials of each part of the full name, but the role of `date` in a name-derived Balance calculation is never explained anywhere.

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 states a specific computation (Balance number) plus the exact input basis (initials of each part of the full name) and names the numerology system (Kabbalistic, Mathers strict). It distinguishes itself from the Chaldean/Pythagorean/Vedic Balance siblings, but never clarifies how 'kabbalistic_strict' differs from the plain 'astroway_numerology_kabbalistic_balance' sibling, which is the closest and most confusable alternative.

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?

There is no statement of when to choose this tool, no prerequisites, and no routing to or away from alternatives. The 'strict' vs non-strict distinction is left entirely to inference despite both tools existing side by side.

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