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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely useful non-annotation context in the cost line (10 credits, Tier 1) and the group label, but discloses nothing about the calculation's behavior or output shape.

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 tight sentences with the core purpose front-loaded, followed by compact bracketed metadata for group and cost. No wasted prose; the only slight redundancy is restating 'Numerology' in the group tag.

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 no explanation, and annotations cover the safety profile. However, the unexplained required 'date' parameter and the absence of any usage routing between the many numerology siblings leave gaps for an agent deciding whether and how to call this.

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 50%: 'fields' and 'precision' are documented in-schema while 'name' and 'date' are bare. The description partially compensates by clarifying that 'name' should be the full birth name, but leaves the required 'date' parameter entirely unexplained (why a vowel-based calculation needs a date is unclear).

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 (calculate), a specific resource (Soul Urge number), and the derivation method (from the vowels of the full birth name). The '[Group: Numerology: Pythagorean]' tag distinguishes it from the Chaldean, Kabbalistic, and Vedic soul_urge siblings, though it does not name a sibling explicitly.

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 choose this over astroway_numerology_chaldean_soul_urge, astroway_numerology_vedic_soul_urge, or the many other soul_urge variants. The description states what it computes but never addresses selection between alternatives.

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